Enterprise

AFFiNE Enterprise: Private Cloud, Self-Hosted, and Secure Team Workspace

Docs and whiteboards on infrastructure you operate. AI is optional and uses configured providers; review data flows before enabling it.

  • Data stays on your infrastructure
  • Offline & intranet licensing
  • SSO via OIDC
An AFFiNE team workspace with structured documents and database views, deployed as a private instance

Built for teams where data location is non-negotiable

AFFiNE can run its editor, docs and whiteboards on infrastructure you operate, including your servers, object storage and PostgreSQL. Self-hosted AI is optional and requires configured provider keys.

For larger or restricted-network deployments, discuss licensing, procurement and architecture with the sales team.

What an enterprise deployment gets you

Data residency by default

Workspace docs and uploads stay on your infrastructure: local filesystem, your own S3-compatible bucket or Cloudflare R2, plus a PostgreSQL you operate.

Storage configuration docs

Deploy where you need

Docker Compose is the officially supported path — one release-tagged config runs the full stack on a VPS, in your datacenter, or inside your private cloud.

Deployment guide

Offline & intranet licensing

An Installable License activates team seats straight from workspace settings — no calls to AFFiNE's license servers. Built for restricted networks.

Team license docs

Sign in with your identity provider

SSO via OIDC, plus Google and GitHub OAuth. Workspace roles and per-document access levels keep editing and review separate.

OAuth & OIDC docs

Bring your own AI — or run none

AI is optional. Workspace owners can add their own provider keys (BYOK); admins can allow OpenAI-compatible endpoints, and AI can be turned off server-wide or per workspace.

AI configuration docs

Backups you can verify

pg_dump for the database, the blob directory for uploads, exported configuration — and a documented test-restore to prove it all works.

Backup & restore docs

Procurement, contracts and licensing

Enterprise agreements are custom by design — scoped on a call, not a checkout page.

  • Custom contracts and invoicing for larger deployments
  • A dedicated point of contact through evaluation and rollout
  • Security review support — the editor is MIT-licensed and auditable
  • Self-host and cloud hybrid options, with SLA available on request
  • Commercial Code License for OEM, white-label and embedded use
Compare plans on the pricing page

From pilot to rollout

Most enterprise evaluations follow the same four moves. We can walk them with you, or you can run them self-serve from the docs.

  1. Scope a pilot

    Pick one team and a real workload. A pilot workspace with genuine docs and boards tells you more in two weeks than a feature checklist ever will.

  2. Deploy on your infrastructure

    Stand up the Docker Compose stack in your environment, connect storage and PostgreSQL, and wire sign-in to your identity provider via OIDC.

  3. Bring your content over

    Import from Notion via its HTML or Markdown export. Coming from Confluence or another wiki, bring Markdown or HTML exports — and validate the result inside the pilot before wider rollout.

  4. License and scale

    Free self-hosting covers up to 10 seats per workspace. Beyond that, activate a Team subscription — or an Installable License for restricted networks — and expand team by team.

Frequently asked questions

Where does our data live if we self-host AFFiNE?

On infrastructure you operate. Workspace docs and uploaded files are stored on the server's filesystem by default, with out-of-the-box support for S3-compatible object storage and Cloudflare R2, and the database is a PostgreSQL instance you run. Storage locations are set through the admin panel and environment configuration.

Can AFFiNE run in an intranet without internet access?

For networks that cannot reach AFFiNE's license service, an Installable License activates offline from workspace settings. It is available through sales.

Is AFFiNE open source?

The editor and most client code are MIT-licensed. The backend and native server components are source-available under the AFFiNE EE license. Contact sales about commercial source-code licensing for OEM, white-label or embedded use.

Which single sign-on options are supported?

Self-hosted AFFiNE supports sign-in via OIDC, plus Google and GitHub OAuth, configured from the admin panel. If your policies require multi-factor authentication, enforce it at your identity provider — AFFiNE delegates authentication to the IdP you connect.

How does enterprise pricing work?

Self-hosting is free for up to 10 seats per workspace. Team is $10 per seat per month billed annually or $12 billed monthly, with 100 GB plus 20 GB per seat and priority support. Contact sales to discuss larger or restricted-network deployments.

Can we use our own AI models, or turn AI off?

AI is optional. Workspace owners can add their own OpenAI, Anthropic, Gemini, or FAL keys (BYOK); admins can allow OpenAI-compatible endpoints. AI can also be turned off server-wide or per workspace.

Private AI for business

Do you support SAML or SCIM?

Not today; use SSO via OIDC with your identity provider, which can enforce MFA.

Talk through your deployment

Bring your seat count, network constraints and security review questions so the team can discuss deployment options and contract requirements.

Last updated: October 3, 2026