Start free. Scale by seat.
Individual is free, capped for a single user. Team adds seats and removes the cap. Enterprise adds the entitlements a bigger org actually asks for: your own identity provider, read-only context sharing, configurable retention, and connectors that bring your data sources, including Google Drive, SharePoint and OneDrive, into memory. Every tier runs the same engine and the same core tool surface.
One person, one shared memory across every project they work in. Hard-capped, not metered — nothing to be billed for.
- Full context model: org + personal contexts
- Semantic search, every core tool
- Federated OIDC sign-in
- At the cap, calls are refused — never silently dropped
A whole team sharing memory across their projects, billed per seat with no hard usage cap.
- Everything in Individual
- Context-linked skill distribution across your team's tools
- Usage billed, not hard-capped
owner/admin/memberroles, restricted contexts
For organizations that need the entitlements below — bring-your-own identity, read-only sharing, configurable retention, or data source connectors.
- Everything in Team, plus:
custom_oauth— bring your own OIDC / SSO provider, configured by your admins in the portal- Read-only context sharing — grant a teammate view-only access to a restricted context
retention_archive— configurable retention & archival, beyond the platform default- Connectors (
background_scanners) — sync Google Drive, SharePoint and OneDrive into memory automatically, kept current in the background - Optional AI distillation of synced documents, billed from prepaid credits
A thought is one saved note (capture_thought/update_thought). An
embedding call is one semantic-search or capture operation against the embedding model. Individual's caps are
hard: usage above them is refused, not billed. Nothing on this page is a binding quote until you're through onboarding.
The same engine and tool surface at every tier.
▸Semantic search, not keyword
Every tier embeds with Vertex AI's gemini-embedding-001 — search finds thoughts by meaning, not just exact words.
▸Federated sign-in
OIDC through any standards-compliant identity provider, on every tier — no shared secrets to manage.
▸Real org & role model
owner/admin/member roles and per-context access grants, not a single shared account.
▸Fails closed
Individual's usage caps return an explicit error when hit. Nothing is silently dropped or served uninspected.
What people usually ask before signing up.
How do I actually sign up?
Self-serve, through the customer portal, on every tier: sign in, create your organization, and Individual is active immediately — no card needed. Team and Enterprise are the same flow, then an Odoo-hosted checkout to add your card; we never handle card data directly. Prefer the API? The same bootstrap it's built on works too — see documentation.
What counts against the Individual cap?
Thoughts saved (capture_thought/update_thought), embedding calls (search and capture both call the embedding model), and total stored content size. All three reset monthly.
Can we move from Individual to Team later?
Yes. Your context ids, org id, and every thought already captured stay exactly as they are — moving tiers changes billing and caps, not the data.
How does billing work?
Team and Enterprise are billed per seat, per month, through our billing partner Odoo — the same billing infrastructure DFENS AI Ltd already runs for dfens.ai. We never handle card data directly.
Where is our data stored?
You choose a data-residency region at org creation: europe-west1, us-central1, or asia-northeast1. Each is a genuinely separate deployment, not a latency fan-out.
What do the connectors sync?
An Enterprise entitlement. An org admin connects Google Drive (shared drives or folders) or Microsoft 365 (SharePoint sites, with every document library, or OneDrive) and maps each source to one context. Documents are chunked, embedded and kept in sync as they change or are deleted; search results link back to the source file. Text, Markdown, CSV, JSON, HTML, and Word, PowerPoint and Excel files are supported. PDFs are not extracted yet and are skipped.
What is AI distillation, and how is it billed?
Optional, per organization, and off by default. Instead of storing raw chunks, connectors can distil each document into focused notes with topics and people. That uses AI model calls, which are metered per organization and debited from a prepaid credit balance (1 credit = £1). If the balance runs out, distillation pauses and resumes when credits are added; plain syncing is unaffected. Credits are currently added for you by our team rather than bought in the portal. Each org also has a monthly cap on synced chunks and a cap on sources.
Who can see synced documents?
Anyone with access to the context a source is mapped to — which may be more people than could open the original file. Map sensitive sources to a restricted context. Per-document permission mirroring is not available yet.
Start on Individual free.
Every tier is self-serve through the customer portal — sign in, create your organization, and you're through in minutes. Team and Enterprise checkout is Odoo-hosted; we never see your card. Questions first? Get in touch and we'll walk you through it.
hello@integratedai.co.uk