Self-host
Run the one-click image in your own AWS account. Your keys, your tenant, your region. You pay your cloud provider and your model providers; nothing reaches us.
Deploy on AWS Marketplace
Marketplace image: free software, just cloud compute.
Grengin Cloud: one flat fee, fully managed. No seats, no minimums.
Same software either way. You choose how involved we are.
Run the one-click image in your own AWS account. Your keys, your tenant, your region. You pay your cloud provider and your model providers; nothing reaches us.
Deploy on AWS MarketplaceWe run the same image for you, in the region you choose. Bring your own provider keys; we store them encrypted and never mark up a token. No seat counts, no minimums, no named plans.
Launch on Grengin CloudEverything the two paths do differently, including the row that is not in our favour.
| Question | Self-host | Grengin Cloud |
|---|---|---|
| Where does the app run | In your AWS account, in the region you pick. | In our AWS account, in the region you pick. |
| Is Perter in the data path THE REAL TRADE | No. Prompts and documents never leave your tenant. | Yes. We operate the app, so your traffic passes through it. |
| Where are model keys | In your tenant. You hold them; we never see them. | Stored encrypted in our vault. Still your keys, still your provider bill. |
| What it costs | Free. You pay your cloud and your model providers, nothing to us. | Flat fee per workspace, plus your model providers. Never per seat. |
| Who patches it | You do, when you pull a new image. Old versions keep working. | We do, continuously. You are always on the current release. |
| Proof of no lock-in | Same image, same schema, same export as Cloud. Read the source. | One-click export into your own cloud. Your data comes with you. |
There's no "enterprise tier." Every deployment, free or managed, ships with the full feature set:
The rule we hold ourselves to: free is everything you need to run a governed AI workspace. Paid is only ever services and new capabilities, never the core.
Grengin connects to model providers using your own API keys. You pay each provider directly for what you use. Grengin adds no markup and doesn't resell tokens. Connect any or all of:
One governance, cost-tracking, and policy layer across all of them.
Grengin is free and supported by the community, through Community posts and the documentation, for every way you run it.
MSPs, consultancies, and platforms can deploy, host, resell, or embed Grengin under the partner program. Deploying inside a client's own tenant is free; hosting Grengin for third parties or white-labeling it needs a partner agreement, and that is the point: your paid offering cannot be undercut by a free copy.
On either path you bring your own API keys and pay model providers directly—we never mark up a token. Self-host the AWS Marketplace image (or build from source) and every request goes straight from your tenant to the provider: Perter is never in the data path. Grengin Cloud is the one exception, stated plainly: we operate the app, so traffic passes through systems we run. Same software either way, and you can export from Cloud into your own account whenever you choose.
Free. There is no seat ceiling, no usage ceiling and no feature flag that trips at a certain size. The AWS Marketplace image and build-from-source path are both free under Apache 2.0—you pay only your cloud compute and your model providers. The governance features are in the repository with everything else.
No, never—on either path. Self-host has no Grengin charges at all. Grengin Cloud is a flat fee per workspace, not per seat. Add your whole team at no extra cost.
The workspace, not the people in it. Add a hundred users on Monday and the invoice does not move. Ask us and we will quote the workspace in one email.
No. You bring your own OpenAI, Anthropic, Google, Mistral, Groq or Cerebras keys and pay those providers directly, at their list price. We never sit between you and the token bill—on Cloud or self-host.
When you self-host the AWS Marketplace image (or build from source), no: requests go straight from your tenant to the provider and Perter is never in the data path. Grengin Cloud is the one exception: we operate the app, so traffic passes through systems we run. We say that plainly rather than hiding it.
You export, run the same image in your own account and carry on. That is the whole point of the two paths being the same software.
Yes. Grengin Cloud is the managed path: we run the same software for you, with your own API keys and your choice of region. Prefer to keep infrastructure in your account? Deploy the free AWS Marketplace image instead.
Yes. Apache 2.0 permits hosting, resale, redistribution, and embedding. Use your own branding for forks and third-party services; the optional partner programme adds official branding, referrals, support, and co-marketing.
Have questions about the license itself? See the Licensing page.
Launch on Grengin Cloud, or deploy the AWS Marketplace image into your own AWS account.