Minute (i.AI)
Open-source meeting transcription and minute generation developed for public-sector use.
4 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Terraform
Runs in
Documented customer environment
AWS ECS application and worker services, database, SQS, storage and separately configured speech and language-model services.
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Terraform ECS ↗ · Source checked 2026-11-19
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Terraform |
|---|---|
| Infrastructure | Servers / containers AWS ECS application and worker services, database, SQS, storage and separately configured speech and language-model services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Open Source / Open Core MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
| License | MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The ECS recipe injects an AUTH_API_URL from shared infrastructure. The public application and Terraform references reviewed do not establish a complete supported SAML/OIDC federation setup for an independent adopter. Obtain the authentication-service configuration, identity-provider compatibility and access lifecycle; a service URL is not proof of corporate SSO.
Incubating project with separate shared authentication service; federation unresolved · Source ↗ · Project scope and external infrastructure runbooks ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The reviewed source supplies deployment configuration for AWS ECS application and worker services, database, SQS, storage and separately configured speech and language-model services. Set organization-specific secrets, networking, storage and compatible image versions before use.
Minute (i.AI) deployment example; review the full linked installation instructions · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-19
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The public ECS recipe configures its backend task at 4 vCPUs/8 GiB in the production workspace and 2 vCPUs/4 GiB elsewhere. Frontend, processing services, database, shared infrastructure and speech/model services add resources. These are project defaults for an incubating system, not tested capacity for another organization or HA design.
Upstream ECS backend-task example; remaining application and model services excluded · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Minute (i.AI); software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
The project is explicitly in incubation. Government and council reports establish pilot use; the public Terraform depends on environment, identity and shared-platform resources that an adopting organization must supply. Azure Speech and language-model calls can send recording or transcript data outside the AWS application boundary. Human review remains necessary for formal minutes.
Community & maintenance
The institutional source identifies actual use, public governance or a named community-support program. The linked application source separately establishes installation and licensing.
Category fit
- Board & committee governance
- Open-source meeting transcription and minute generation developed for public-sector use.
- AI tools & infrastructure
- Open-source meeting transcription and minute generation developed for public-sector use.
Compare within Board & committee governance
- BeleniosSelf-hosted verifiable online voting with separated election administration, credential and trustee roles.
- Azure
- BoardPAC On-PremiseCustomer-hosted board meeting and governance platform with role-based meeting access.
- Azure
- FormKiQ Board and Committee Governance Directory PublisherManage board meeting documentation, agendas, resolutions, minutes, and committee records with controlled access, version management, and long-term retention.
- AWS
- Helios VotingOpen-source verifiable election software for organizational and committee voting.
- Heroku
- Fly.io
- Indico (CERN)CERN's meeting, conference and agenda-management application deployed through a community Railway recipe.
- Railway
- OpenSlidesSelf-hosted assembly governance for agendas, motions, elections and meeting participation.
- Railway
These products address related workflows; read their category-fit notes before comparing scope. See all of Board & committee governance →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Terraform ECS ↗raw.githubusercontent.com
- Repo (Incubation Notice) ↗github.com
- MIT ↗raw.githubusercontent.com
- Commits ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Terraform ECS ↗ · AWS
Institution deployment · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
AWS ECS application and worker services, database, SQS, storage and separately configured speech and language-model services. The project is explicitly in incubation. Government and council reports establish pilot use; the public Terraform depends on environment, identity and shared-platform resources that an adopting organization must supply. Azure Speech and language-model calls can send recording or transcript data outside the AWS application boundary. Human review remains necessary for formal minutes.
- Terraform ECS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community, governance or adoption evidence ↗knowledgehub.dev.ai.gov.uk
- Upstream project ↗github.com