Self-hosted in your cloud
Greenlight installs into Azure, GCP, or AWS using a versioned provider package. Your data and end users stay inside the cloud boundary your team controls.
For security reviewers
Greenlight is self-hosted in your Azure subscription, Google Cloud project, or AWS account, authenticated through your identity provider, and runs on infrastructure your team controls. It gives IT a continuous, auditable governance plane over the apps your employees build with coding agents.

Self-hosted in your cloud
Greenlight installs into Azure, GCP, or AWS using a versioned provider package. Your data and end users stay inside the cloud boundary your team controls.
Authenticated by your IdP
OIDC SSO integrates with Entra ID, Okta, and Google Workspace today. SAML and SCIM are coming soon.
Every change is reviewed
Apps are delivered through pull requests, and every pull request runs through a single Greenlight policy check that covers committed secrets, dependency vulnerabilities, and your org policy bundle.
Every action is audited
An append-only audit log records platform, agent, and IT actions. Search, export, SIEM forwarding, and tamper-evident chaining are on the roadmap.
In your Azure subscription, Google Cloud project, or AWS account, behind the network boundary created for Greenlight. The control plane, data broker, and deployed apps run together inside that boundary. See Network isolation.
Whoever your identity provider says maps to the org_admin role. Greenlight has no superuser account, no recovery key for Shift staff, and no shadow directory of its own. See Identity, SSO & RBAC.
Integration credentials and sensitive environment variables sit in your cloud’s managed secret store—Key Vault, Secret Manager, or Secrets Manager—never in the control-plane database. Apps authenticate using workload identity rather than static cloud credentials. Admins can see that a secret exists; they cannot read its value. See Secrets management.
Every platform, agent, and IT action emits an audit event with actor, target, diff, and reason. The log is append-only today. Audit search, CSV/JSON export, SIEM forwarding, WORM storage, and HMAC chaining are coming soon. See Observability & audit.
The control plane is a small set of HTTP services your IT team operates inside your cloud. The data broker proxies outbound calls but does not hold plaintext credentials beyond the in-memory exchange window. A full breakdown of actors, trust boundaries, and scenarios lives in Threat model.
Greenlight is built to integrate cleanly with the compliance frameworks your organization already operates under. The platform’s role is to produce governance evidence inside the customer-owned install; certifications belong to the operating organization. Formal compliance packets are coming soon. See Compliance.
Running apps continue to run. They have their own pods, their own data, and the data broker keeps serving cached integration metadata through a typical control-plane outage. New deployments and policy changes pause until the control plane recovers, and killing an app remains possible via the cloud provider’s normal Kubernetes controls even with Greenlight offline.