Comparison · Self-hosted vs Managed

Consortium vs WorkOS

WorkOS is Free (up to 1M MAU). Consortium is a self-hosted alternative at $2.99/mo. Here's when each makes sense.

Try Consortium Free Consortium overview
ConsortiumWorkOS
HostingSelf-hosted, your infraManaged SaaS (cloud only)
Data locationYour server, your diskWorkOS's cloud
Free tier3 tenantsFree
Pro pricing$2.99/moFree (up to 1M MAU)
DependenciesNone (single binary + SQLite)N/A (managed)
Setup time~30 secondsAccount signup
DashboardBuilt-in at /uiCloud dashboard
LicenseBSL 1.1Proprietary SaaS
When to use Consortium

Pick Consortium when you want simplicity and ownership.

Consortium is a single Go binary with embedded SQLite. Install it with one command, and you are running in under a minute. Your data stays on your server.

curl -fsSL https://stockyard.dev/consortium/install.sh | sh
Install Consortium Consortium docs

WorkOS makes sense when you need more.

WorkOS handles enterprise authentication — SSO, directory sync, admin portal. If your SaaS sells to enterprises that require SAML SSO, WorkOS solves that. Consortium handles multi-tenant data isolation and config, not authentication.
Deciding between the two

Before choosing between Consortium and WorkOS, consider what happens when you need to leave. WorkOS exports vary in completeness — some fields, some history, some metadata may not come with you. Consortium stores everything in a single SQLite file. Leaving means copying that file. This is not a hypothetical concern: the average team changes tools every 18 to 24 months.

Architecturally, Consortium and WorkOS could not be more different. WorkOS runs on distributed cloud infrastructure with load balancers, managed databases, CDNs, and redundancy across availability zones. Consortium is a single process writing to a single file on a single disk. That sounds fragile until you realize that SQLite handles more concurrent readers than most web applications will ever need, and WAL mode means reads never block writes.

Moving to Consortium

Switching from WorkOS to Consortium is straightforward for most teams. Export your data from WorkOS (most services offer CSV or JSON export), then POST each record to Consortium's API. A migration script that reads the export and writes to /api/ endpoints typically takes less than 50 lines of code. The reverse migration is equally simple — Consortium's SQLite database is a standard file you can query with any SQLite client.

FAQ
Is Consortium a WorkOS alternative?
WorkOS does enterprise SSO and directory sync. Consortium handles multi-tenant data isolation. Different problems — you might need both.
Does Consortium handle SSO?
No. Consortium manages tenant data isolation. For SSO (SAML/OIDC), WorkOS or Authentik are necessary.
Related

Consortium overview

Get started

Self-hosted multi-tenant SaaS kit in 30 seconds.

Single binary. Free to start. $2.99/mo for Pro.

Install Consortium All 150 tools for $29/mo →