Who uses Greenlight

Personas

Greenlight is shaped around three roles. Each gets the surface that fits their job, and each is governed by the same audit and policy plane.

Citizen developer

Builds applications by talking to a coding agent. Doesn’t write Dockerfiles. Doesn’t touch Kubernetes. Knows the business problem; trusts the platform to make the app real and safe.

IT admin

Owns the install, the integrations, the audit log, and the kill switch. Operationally literate. Says yes more often when yes is auditable.

Coding agent

Speaks MCP. Reads Knowledge for context. Calls platform tools to register apps, propose policies, open pull requests. Has scoped powers — never god-mode.

Who doesn’t use Greenlight (yet)

End users of the built apps just see the app. They sign in through your identity provider and use what the citizen developer built. They never touch the Greenlight dashboard, the agent plugin, or any platform tooling.

Note

Most apps deployed on Greenlight today are internal employee-facing tools, where end users are members of the operating organization. Externally accessible apps — those intended for customers, partners, or the public internet — are on the roadmap and will introduce additional identity, ingress, and rate-limit controls.

Next

How it works The five-step tour from idea to production.

For Builders A short, command-free guide for citizen developers.

For IT Admins Operationally explicit guidance for the install and run.