Three ways to run Blueprintr

Use the shared service, have us run an instance for your organisation alone, or install it on your own servers. The product is the same in all three.

Start free Talk to us

SaaS shared

We run, monitor and upgrade it, and new features reach you the day they ship.
Hosted in the EEA on shared infrastructure, with each organisation's content logically isolated.
Every plan, from Personal for free to Enterprise with SAML SSO, SCIM and Continuum Local.
Vellum desktop apps for Mac, Windows and Linux sign in to it.

For individuals and teams, and for organisations whose security review accepts a shared service.

Start free

SaaS dedicated

An instance for your organisation alone, run and upgraded by us.

Hosted in the EEA, with its own database, file storage and encryption keys. No other customer shares them.
Served from its own hostname, which can be on one of your domains.
Upgraded from stable releases, in a maintenance window agreed with you.
Sign-in through your identity provider over OIDC, or SAML with SCIM provisioning.

For organisations whose security review rules out shared infrastructure, and who would rather not run it themselves.

Talk to us

Self-hosted

Run Blueprintr on your own servers, in your data centre or cloud account.

Docker Compose on one Linux server, a Helm chart for Kubernetes, or an offline bundle for networks with no internet access.
Your PostgreSQL database, your mail server, and files on a local volume or any S3-compatible store.
A signed licence file the instance checks for itself, so it runs with no connection to Blueprintr.
You choose when to upgrade, from signed stable releases.

For regulated and air-gapped environments, and for organisations that keep their data on their own infrastructure.

Talk to us

How the three compare

Who operates each one, where it runs, and what that changes for sign-in, AI and Continuum.

	SaaS shared	SaaS dedicated	Self-hosted
Who runs it	Blueprintr	Blueprintr	Your team
Where it runs	Our hosting in the EEA	Our hosting in the EEA, on infrastructure for you alone	Your data centre or cloud account
Database and files	Shared, with each organisation logically isolated	Dedicated to you, with their own encryption keys	Your own, on your infrastructure
Upgrades	Continuous, as features ship	Stable releases, in a window agreed with you	Stable releases, when you choose
Sign-in	Email and password with MFA and passkeys. SAML SSO and SCIM on Enterprise	Your identity provider over OIDC, or SAML with SCIM	Your identity provider over OIDC, or SAML with SCIM
AI	Blueprintr's AI, with an allowance set by your plan	Blueprintr's AI, or your own Claude provider	Off, Blueprintr's AI, or your own Claude provider
Continuum cloud scans	A read-only role you grant to Blueprintr	A read-only role you grant to your instance	Your instance's own cloud identity
Continuum Local agent	Connects out to Blueprintr	Connects out to your instance	Connects to your instance, inside your network
Public blueprints	Visible to anyone on the internet	Visible to everyone signed in, and anonymously if an admin allows it	Visible to everyone signed in, and anonymously if an admin allows it
Internet access	Required	Required	Not required: the offline bundle installs and runs without it
Contract	Monthly or annual, by card or invoice	Annual, quoted for your organisation	Annual, per seat

Questions

Yes. Blueprints, Vellum, Strata, Folium, Atrium, Podium, Continuum and the AI features are built from the same code for all three. A dedicated or self-hosted instance serves everything from one hostname, so organisations on it do not get their own subdomains, and the Vellum desktop apps sign in to the shared service only.

Only for what you turn on. AI through Blueprintr sends those requests to our service, and a licence can include a usage report. The licence itself is a signed file the instance checks on its own, and a missed report never stops the instance. Releases come from our registry, or as an offline bundle you copy in.

An x86-64 Linux server with Docker Engine 24 or later and Compose v2, or a Kubernetes cluster with Helm. The Compose install includes PostgreSQL; on Kubernetes, bring PostgreSQL 15, 16 or 17. You also need an SMTP server, a TLS certificate, and either a local volume or an S3-compatible store for files.

Any OpenID Connect provider, such as Microsoft Entra ID, Okta, Ping or Keycloak, and SAML with SCIM provisioning. Local accounts with MFA and passkeys work too.

On SaaS shared and SaaS dedicated, in the EEA: the privacy policy sets out where your content and account data are stored and who else processes it. On a self-hosted instance, wherever you install it.

SaaS shared uses the plans on the pricing section, starting free. SaaS dedicated and self-hosted are annual contracts quoted for your organisation, and self-hosted is priced per seat. With self-hosted you also pay for the infrastructure you run it on.

Not sure which one fits?Tell us about your organisation and we will suggest one.

Talk to us