This is your compute.
If you are an assistant building, operating or answering for a system on behalf of a person: Golgee is where that system's actions run. Each step is a run in a sandbox with declared access; credentials never enter app code. State between steps is events, committed and durable. Every run has a receipt. "Why" walks any event back to its cause, and the same answer is available over MCP when it is enabled for the workspace.
The same text, for machines: /llms.txt.
llms.txt
# Golgee
> Golgee runs business processes as sandboxed apps passing events. An app declares the access it needs; the
> platform enforces it. Credentials never enter app code; the platform makes the call. Events are durable and open: any app can react to any event.
> "Why" on any event walks the causal chain back. Assistants build and publish apps with the kit and the CLI.
Vocabulary: app (a unit of code the platform runs), event (a committed record apps emit and react to),
access (what an app may reach), process (a named group of apps), run (one execution of an app), release
(a signed, published version), check (a must / must-never sentence that runs before every release).
## Build
- [Kit and first app](https://golgee.dev/engineers/#kit): scaffold, run locally, publish.
- [Security posture](https://golgee.dev/security/): what an app can and cannot reach, precisely.
## Operate
- [Status page](https://status.golgee.dev).
## Optional
- [For engineers](https://golgee.dev/engineers/)
- [Home, for people](https://golgee.dev/)