The operating system for a small AI-first company

One gateway.
Every tool.
A human approves anything that leaves.

ugeco OS puts a single gateway that you own in front of the tools you already run. Claude, the Geco agent and the console all go through it. Every send, publish and spend waits for a person to approve the exact content.

Try the interactive demo Ask for early access
  • Runs on your own infrastructure
  • Append-only audit log
  • Do-not-contact enforced on every send

Diagram: Claude, Geco and the console connect to one central gateway. The gateway alone connects to Slack, Gmail, GitHub, ERPNext, Frappe HR, WhatsApp, Meta Ads, Google Ads, LinkedIn, media generation and the books tool. A send is held at the gateway until a person approves it.

Interactive demo

A mock of the console, in this page.

A simplified mock with fictional data. Approve something, move a deal, open a linked GitHub issue or Slack thread.

Demo data, fictional
Tour

A guided tour starts when this demo scrolls into view. It stops as soon as you use the demo.

Automated workflow Geco is in early access

Geco drafts. A person decides.

Geco is the agent that lives in Slack. It reacts to events, drafts the work and asks. It reaches every tool through the same gateway as everyone else, so the same rules apply to it.

Step 1 of 10 Demo data, fictional
    #launchMock thread

    What the gateway recorded

    Audit log append-only

      How it is built

      Four layers. One of them is the only way through.

      Your tools stay off-the-shelf. What you own is the layer in the middle and the contract every client uses to reach it.

      The one gateway

      Every call from every client lands here first. It checks who is asking, applies policy, holds anything that leaves until a human approves it, writes the audit row and makes sure a retried request is not sent twice.

      Safety by design

      The rules live in one place, so they hold everywhere.

      • You approve the exact content

        An approval covers one frozen payload. If a single character changes afterwards, the approval no longer applies.

      • An audit log that shows tampering

        Every call, allowed or refused, is appended. The gateway cannot update or delete a row, and a hash chain makes any later change detectable.

      • Exclusions that cannot be skipped

        Excluded companies and do-not-contact are checked at the gateway on every outbound path: email, WhatsApp, posts and ads.

      • People see only their own business lines

        Access is by role and business line. A request outside your lines is refused, and the refusal is audited too.

      • Budgets and caps with a hard stop

        Daily send caps and spend budgets are enforced before the call is made. Media generation shows an estimate first.

      • Never sent twice

        Every send carries an idempotency key. A retry, a double click or a replayed webhook returns the first result instead of sending again.

      Connections

      Keep your tools. Own the layer between them.

      Each connection is an adapter behind the gateway, and each adapter ships with a fake, so the whole system runs before you hand over a single credential. A flag switches one connection at a time to the real service.

      Showing fakes: every adapter answers from a built-in double. Nothing leaves the machine.

        Put one gateway in front of your tools.

        Tell us which tools you run today. We will show you which ones already have an adapter and how the gateway sits in front of them, starting on fakes.

        Early access. ugeco builds ugeco OS for its own operations first.

        Ask for early access