Building blocks for a business operating system.

Model and run any business process.

From a single payment workflow to the systems a whole company runs on. Every process is built from the same blocks: small apps passing events. You see every step as it happens and can ask why anything happened. You change the process by telling the builder what to change, in your words. And before any change goes live, your checks run: the things that must happen, and the things that must never happen. If one fails, the release does not go out.

I'm interested

Systems thinking, without the infrastructure. Early access by conversation.

An event says that something happened, such as a payment received, and carries the data that goes with it, from a single value to a whole document. An app receives one event, does one job and emits a new event, and a chain of apps is a process, and apps can call, and hear back from, the outside systems a business already runs, such as payments, a CRM or email. Many processes share events and join up into a whole business, and the view then pulls back to show three layers. Operate is where the apps run, and the outside systems stay connected to it. Audit records every run, so you can trace any outcome back to its cause and replay it step by step. Analyze is one shared store of data from every app, which people, agents and apps use to decide what happens next.

Illustration

01 Build

Two ways to build. One system.

In the Builder, in plain language.

Business users build and edit processes directly in Golgee. Describe the process, or the change you want, to the authoring assistant; it builds the apps, shows you the result and releases it when you approve.

Bring a process

In your IDE, with the tools you know.

Engineers build and edit the same processes from their own editor or coding assistant. Golgee's kit, command line and assistant integrations give those tools what they need to write, test and publish apps.

For engineers

Both work on the same apps and events, so a process started by one can be changed by the other.

02 Building blocks

Events, apps, processes.

Three blocks make everything on Golgee, from one workflow to the whole business.

01 · event

Something happened.

An event says something happened: a payment arrived, a form was sent, a deadline passed. It carries the data that goes with it, as small as a single value or as rich as a document, an image or a video. Events are open, so anything in the workspace can react to one.

02 · app

One job, done well.

An app picks up an event, does one job and emits a new event. It knows nothing about what comes before or after it, so it is easy to build, replace and reuse.

03 · process

Apps, working together.

A process is a chain of apps passing events. Processes share events and apps, so they join up into a system: add one and it connects to everything already running.

An app is small. It is not limited.

data

Its own data, by default.

Every app gets its own datastore: a Postgres database, object storage, a document database, or any mix of the three. Nothing to provision, and no other app can reach in.

interface

A full interface, or none.

An app can carry a rich screen for the people who use it, a simple form, or run completely headless and only speak in events.

integrations

Connected to the systems you already run.

Apps integrate with third-party systems: payments, CRM, accounting, email, your own APIs. Credentials never enter app code; the platform makes the call.

compute

An agent, or plain code.

An app can be an AI agent that reasons its way through a task, deterministic code that does exactly the same thing every time, or both in one process, with the same record and the same controls on each.

03 Try and check

Try it. Check it. Then release.

Nothing goes live on trust. Run a real example through the changed process and watch every step, then let your checks decide whether the release goes out.

A check is a sentence. You do not write tests; you say what must hold:

golgee check · before release
  • PASS"A new invoice must create a reminder in 7 days."
  • FAIL"A paid invoice must never get a reminder."
  • PASS"An invoice over 10,000 must stop and ask for approval."

Each check becomes a run against a scratch copy of your process, and it runs before every release from then on, yours or anyone else's. If one fails, the release does not go out, and you are told in the check's own words.

Builder

'A paid invoice must never get a reminder' no longer holds: the reminder app now runs when status is paid. Was that intended? I can fix the app, or change the check.

A failing check, reported in its own words.

04 Operate and audit

It runs itself. Every run is on the record.

Once released, a process just runs: no servers to mind, no downtime when it changes, and a person in the loop wherever you want one. Everything it does is kept.

run

Always on.

Golgee hosts, scales and watches every app. A new release swaps in without a restart and without dropping work in flight.

approve

People where it matters.

Any step can stop and wait for a person. Sensitive actions do not happen until someone approves them.

why

Ask why.

Pick any event and walk the chain back to what caused it. A customer question gets an answer in minutes.

runs · append-onlyrec
REC

Recorded.

Every run and every event is written down as it happens: the input, the outcome, how long it took and which release of the app did the work. The platform keeps the record, so an app cannot skip it.

VIS

Visible.

Watch events arrive live and open any run. An auditor or a manager sees exactly what the process did, not what someone remembers.

RPL

Re-playable.

Take any recorded run and play it again, step by step, against the process as it was then or as it is now. See exactly what happened, or prove a fix before it ships.

05 Data lake

Every app feeds one data lake.

Data does not stay locked inside the app that made it. As apps run, their data flows automatically into a single data lake for the whole business, already organised and ready to query.

auto

Automatic.

No pipelines to build and no exports to schedule. Every app's records and every event land in the lake as they happen, described well enough that a person or a tool can use them without asking the author.

bi

Open to your BI tools.

Point the reporting and analytics tools you already use at the lake. One place holds billing, operations, support and everything else your processes touch.

use

For people, agents and apps.

Analysts build dashboards on it. Agents answer questions from it. Apps read it to decide what to do next. Everyone works from the same picture of the business.

06 For engineers

If you're the engineer: nothing here is magic, and nothing is hidden.

Every app is code, running in a sandbox that can reach only what its manifest declares. Credentials never enter app code; the platform makes the call. Events stay open: any app can react to any event without the first app changing. A new release of your app swaps in without a restart, and a platform deploy rolls without dropping the work in flight. The engineers page has a worked example of open events, what the platform gives you without building it, and the kit and CLI.

For engineers

07 Early access

Bring a process.

We are provisioning a small number of workspaces by conversation. Tell us about one process your business runs, and what you want it to do.

Early access includes a named workspace, console access, your own apps, and a direct line to the founder. Provisioned after a conversation.

Beta terms agreed before provisioning.

I'm interested