Security & trust
Your data never leaves your environment.
Go Bananas runs inside your own cloud. We do not host it, and we cannot see it.
This page describes a private deployment — how enterprise customers run the platform. The hosted community edition works differently and is covered at the end.
What a private deployment guarantees
Eight commitments your security team can verify.
Because the platform runs inside your environment, none of these needs to be taken on trust — your own team can inspect every one of them.
- 01
It runs in your cloud, not ours
The platform is installed in your own cloud account and operated by your team. We have no standing access: no support tunnel, no vendor login, no telemetry, nothing phoning home. Updates arrive only when your operators pull them, on your schedule.
- 02
The AI runs on your own contract
Every model call goes to a model endpoint in your own subscription — for example Azure AI Foundry — under the terms you already have with that provider. There is no intermediary AI account of ours. If the model key is missing, the platform refuses to run; it never falls back to a public endpoint.
- 03
Your data cannot be used for training
Not merely forbidden by contract — structurally impossible. Your data never reaches us, so there is nothing for us to train on.
- 04
Sign-in through your identity provider
Single sign-on over OIDC or SAML — Microsoft Entra ID, Okta, Ping — with password and social logins off by default. SCIM provisioning removes access automatically when someone leaves. MFA is enforced by your identity provider.
- 05
Code the AI writes runs in a sealed box
Every preview runs in a throwaway, isolated container that holds no credentials and is destroyed automatically. The installer refuses to install onto an insecure configuration unless an operator explicitly overrides it.
- 06
A tamper-evident audit trail
Every action is logged, and the log cannot be edited after the fact. It records what a person did separately from what the AI did: file changes, commands, publishes and guest access.
- 07
You hold the encryption keys
Keys live in your own key vault (for example Azure Key Vault). Destroy a key and the data it protects becomes permanently unreadable.
- 08
You can walk away at any time
Your data stays with you throughout. Source code can be exported to your own Git at any time, and the applications you build run without a license from us.
Network boundary
Only two things leave your network.
Everything else can be firewalled off.
- 1
Downloading the software
Platform images, pulled by your operators when they choose to update.
- 2
Calls to your own model endpoint
In your own cloud subscription, under your existing contract with that provider.
Certifications and independent testing
Where we are, stated plainly.
Because Go Bananas runs entirely inside your environment, your security team can review all of it directly — the deployment, the network boundary, the identity configuration and the audit trail.
We haven't yet completed a SOC 2 audit or a third-party penetration test. We're glad to commission both as part of an enterprise agreement, with any findings addressed under the contract.
Request an architecture reviewThe hosted community edition
A different trust model, and a different audience.
The community edition at gobananas.dev is operated by us, for individuals and small teams. It is not the product described above: your data is processed by us and by the sub-processors below. Client data that must stay inside your environment belongs in a private deployment.
See every third party the community edition usesA private deployment uses none of them: it runs on your infrastructure and your AI provider.
Reporting a vulnerability
Found something? Tell us first.
Email [email protected]. We acknowledge good-faith reports within 48 hours.
Machine-readable contact details (RFC 9116): /.well-known/security.txt
Last reviewed 20 October 2026.