Editions

PromptGate is shipped in two editions. They share the same codebase and the same UI; the difference is who runs it and which features are wired.

Community Edition

• License: Business Source License 1.1 (BSL 1.1)
• Cost: free
• Where it runs: your machines
• Who supports it: the community + GitHub issues
• Source: https://github.com/promptgate-org/promptgate

The Community Edition is single-user by design — there’s exactly one admin account. That keeps the security model simple: every action is yours, every audit entry is yours, every credential is yours.

It includes everything the gateway can do at the protocol / runtime level: all four project types, all eight providers, all guardrails, rate limits, budgets, OAuth connections, MCP, observability, backup. The full feature matrix is on FEATURELIST.md in the repo.

What BSL 1.1 means in practice

The license permits non-commercial and small-org commercial use. It prohibits offering PromptGate as a commercial managed service that competes with the Cloud Edition. After the change date (4 years after release), the same code automatically converts to Apache 2.0.

In plain English:

• ✅ Run it for yourself, your hobby project, your startup, your day job, internally at any company.
• ✅ Modify the source. Contribute back. Fork it. Patch it. Self-host it forever.
• ❌ Wrap it in a sign-up flow and sell it as a hosted gateway. (That’s what Cloud Edition exists for.)

For the exact legal text, see the LICENSE file in the repo.

Cloud Edition

• License: commercial
• Cost: paid (per-user / per-token plans)
• Where it runs: managed by Akyros Labs at https://promptgate.dev
• Who supports it: Akyros Labs

Cloud Edition is the same code with multi-tenant features unlocked:

Feature	Community	Cloud
All four project types	✅	✅
All 8 providers	✅	✅
Guardrails (all types)	✅	✅
Rate limits / budgets	✅	✅
OAuth connections	✅	✅
MCP Bridge / Gateway / Control Plane	✅	✅
Observability (dashboard / metrics / logs / audit)	✅	✅
Webhooks	✅	✅
Backup / restore	✅	✅
Single-user admin	✅	—
Multi-user with RBAC (owner / admin / developer / viewer)	—	✅
Invitations / team management	—	✅
MFA / SSO (TOTP, Google, GitHub, SAML)	—	✅
Org hierarchies (multiple workspaces per org)	—	✅
Billing / per-user pricing	—	✅
Managed updates / SLA / monitoring	—	✅
Log retention	7 days (gateway), 30 days (audit), 14 days (webhook deliveries), 30 days (sessions)	unlimited

Cloud Edition is sold as a SaaS — sign up at https://promptgate.dev when it’s launched, or stay self-hosted on Community.

Which one should I pick?

Situation	Edition
Solo developer / hobbyist	Community
Single-team internal tool	Community
You need multiple users with role-based access	Cloud
You want SSO / MFA / SAML	Cloud
You want someone else to run it	Cloud
You want to keep your data on your own infra	Community
You build for a customer who’ll self-host	Community

If you start on Community and outgrow it, the Backup / Export ZIP gives you a portable JSON dump of every table you can hand to Cloud (or any future self-hosted replica) on import.

How the edition is set

A single environment variable controls everything:

PG_EDITION=community   # default — what you get from the public repo
PG_EDITION=cloud       # only set on Akyros-managed deployments

The flag is read by config/edition.php and surfaces through:

• App\Services\Edition\Edition::isCommunity() / ::isCloud() for runtime checks
• @editionIs('community') Blade directive for view-level gating
• Retention caps in config('edition.retention.*'), applied daily by the promptgate:prune Artisan command

If you self-host, leave it on community. The retention policy keeps the SQLite/Postgres footprint small without needing manual DELETE jobs.

Plugins

Both editions will support the plugin marketplace (currently 📋 — see Plugins). Plugins ship as signed packages and extend providers, guardrails, alert sinks, and OAuth flows.

---

Next: Projects — the top-level container.

---

© Akyros Labs LLC. All rights reserved.