The same product, without the servers

Hosted

No credit card to start

Identical codebase, run by us on European infrastructure. Sensible when you want the workspace and not the operations - and you can still take it in-house later, because it is the same thing you could have installed yourself.

What we run for you

The parts you would otherwise be on the hook for

European infrastructure

Kubernetes on Scaleway, a European provider, in EU data centres by default - with the honest caveat that this holds unless you pick a model or feature whose provider sits outside the EEA. Managed PostgreSQL with pgvector and managed Redis, both run as managed services, plus TLS certificates renewed for you.

Updates without a maintenance window

New versions land without you scheduling anything, and without a migration you have to run yourself.

Your identity provider, here too

OAuth sign-in with Google, Microsoft Entra ID and Nextcloud works identically hosted and self-hosted, so hosted does not mean a separate user directory to maintain. Entra group sync needs an enterprise-app registration pinned to your tenant; on the hosted version that is arranged per deployment rather than self-service — ask us before you plan around it.

Billing that lives in the product

Plans, invoices, seat counts and usage against your monthly budget, all in Settings rather than in an email thread.

The compliance hub

15 GDPR checks and 6 EU AI Act checks against your live configuration, plus the DSR intake and DPIA registers.

Dutch legal sources, maintained

A knowledge base of Dutch and European primary sources that we keep current. It exists only on the hosted version, because keeping it fresh is our job.

How your data is separated from everyone else's

Worth being precise about

Organisations share a database, and every tenant-scoped query filters on your organisation id - there is no separate database or schema per customer, and we would rather tell you that than imply an isolation model we do not have. On top of it sits the same encryption the self-hosted product uses: AES-256-GCM under an Argon2id-derived key, with an OPAQUE path available so a migrated account's password never reaches the server at all. If that is not enough separation for your risk appetite, self-hosting is the honest answer, and it is the same software.

Getting started

What signing up actually involves

Create the organisation

No credit card

You verify your email address with a link that expires after a day, and accept the terms and privacy policy explicitly rather than by implication. The free tier needs no checkout at all.

Connect what you already use

Google Workspace, Microsoft 365, Nextcloud

Each person connects their own account, and an assistant acts with that person's permissions - never more. Nothing is connected organisation-wide by default.

Pick a plan when you outgrow the free one

Upgrades take effect immediately and are prorated; downgrades take effect at the end of the period you already paid for. Where a trial is offered it needs no card and cancels itself rather than rolling into a charge.

Sub-processors

Who else touches your data, and under what

What the hosted version does not promise

The part most vendors leave out

There is no published uptime percentage and no service level agreement - our terms say the service is provided as-is, and quoting a number we have not committed to would be worse than saying nothing. We hold no ISO 27001 or SOC 2 certification. Backups run with a defined retention and rotation, but we publish no recovery-time objective. If your procurement process needs any of those in writing, tell us what it needs and we will answer honestly rather than aspirationally - and for some organisations the right answer will be to self-host.

FAQ

Hosted vs. self-hosted

Is the hosted version a different product?

No - the same codebase and the same container images. What differs is who operates it and how paid access works: a subscription on our cloud, a licence key on your own servers.

What can I do on the hosted version that I cannot self-host?

Billing and subscriptions, the compliance hub, the website builder and its analytics, and the maintained Dutch legal-sources knowledge base. Those are operator surfaces that only make sense where we run the operation.

And the other way round?

Self-hosting gives you the Azure services panel, unsandboxed test execution, and - the big one - no usage caps of any kind, because the model bill is yours rather than ours.

Where exactly is it hosted?

Scaleway, a European provider, in EU data centres. We deliberately do not name a specific city on this page: the region is deployment configuration, and we would rather under-claim than state something we cannot evidence. Ask and we will tell you the current region in writing.

Can we move to our own servers later?

Yes. Websites, knowledge bases and automations export to files, your content is yours, and the self-hosted install is one command. Leaving is a decision, not a project.

Do you train models on our data?

No. Where a model provider offers no-training or zero-retention terms we have them enabled. The stronger technical control is to point the workspace at a local model, which self-hosting allows and which means nothing leaves your network at all.

Try it hosted, move it in-house if you want to

The free tier needs no card, and nothing you build is locked to our servers.