SaaS or self-hosted
Which deployment fits, and what each includes.
One binary, two ways to run it
The SaaS and the self-hosted install are the same static Go binary with the same product — boards, recorders, the work queue, the task engine, MCP, the skills. What differs is who runs it, where the data lives, and whether plans are metered: the SaaS enforces each organization's plan, while a self-hosted install runs every organization on Enterprise limits unless you turn metering on.
The SaaS
app.vitrinka.ai: create a workspace, invite the team, done. Nothing to operate, upgrades land as they ship. Membership pays for the platform. Storage and seats are shared across the organization's workspaces. Current monthly prices and enforced quotas are on the pricing page; prices exclude applicable VAT.
| Plan | Intended use |
|---|---|
| Free | Try the platform without a payment card |
| Starter | Individuals and small teams; optional purchased AI credits, with no monthly AI bonus |
| Pro | More shared storage and seats for ongoing product work, plus monthly AI credits |
| Team | More room for an organization running several products, plus a larger monthly AI bonus |
| Enterprise | Negotiated limits and deployment requirements |
Managed AI uses a separate prepaid balance. Pro and Team include the monthly amounts shown on the pricing page; Starter can buy credits too. Your own AI connection is billed directly by your provider. Free includes no managed AI trial bonus.
100 credits = $1, with usage charged at 2× actual provider API cost. Included bonuses renew with successful subscription payments and expire at the end of each billing period. Purchased credits carry forward and survive membership changes. Top-ups are manual, with no automatic refills. Exhausting the balance pauses managed AI while boards and collaboration continue.
Pick it when nobody wants to run a server and your data may live on managed EU infrastructure — where it lives and how it is protected is the Security tab.
Self-hosted
One container on one host you own — built for strict-security environments, up to air-gapped networks that never reach the internet:
- OIDC single sign-on against your own directory — an identity provider on your internal network included (Single sign-on) — with role mapping and verified MFA.
- Workspace RBAC — every request authenticated and role-gated.
- Per-workspace encryption for sensitive content fields and blobs, sealed database backups and cryptographic deletion.
- Retention — configurable deletion with a recovery window for recorded sessions.
- Audit log — append-only, committed with the action it records.
- Enterprise limits, unmetered — every organization gets 500 GiB of pooled storage, unlimited seats and 250,000 active boards per workspace, unless
VITRINKA_METERED=1enforces each organization's plan. With sign-up open, every new account's own organization gets that allowance too, so gate new accounts withVITRINKA_WAITLIST=1(the first admin). - An offline licence — verified on the host, with no licence server and no phone-home; an expired one pauses writes after a 14-day grace period, keeps reads working and never loses data (Licensing).
Install is a Compose file and two env values: installing on your own host. SSO, configuration and operations have their own pages under Operator; licensing and the guarantees are spelled out under Security.
Outbound integrations are optional and env-gated by design — an air-gapped install loses nothing except the calls that would have left the network.
Which to pick
| You | Take |
|---|---|
| A team that wants boards today, no ops | SaaS |
| Compliance requires data on your infrastructure | Self-hosted |
| An air-gapped or bank-grade network | Self-hosted |
| Trying vitrinka before committing either way | SaaS Free — the binary is the same, so nothing you learn is wasted |