Introduction
Catentio is a multi-agent operator platform — the SaaS face of the catentio agent runtime. A single Catentio workspace gives you a fleet of named agents (cimi, tora, sai, ren, fumi, iro…) that you can invoke from the portal, the CLI, the API, or programmatically from another product over the Forjio family bus.
This documentation covers the developer-facing surface: signing in, invoking an agent, running a project pipeline, watching runs, and integrating Catentio into your own code via the SDKs.
New to Catentio? Start with the Quickstart — you'll have an agent run completed in about five minutes.
What's here
The docs are organised by how you'll use the product over time:
- Getting started — sign in, install the CLI or SDK, invoke an agent end-to-end.
- Core concepts — workspaces, agents, runs, projects, tools, skills, memory, heartbeats.
- Authentication — Huudis SSO, the Catentio session model, and the chat-bubble session bound to your portal identity.
- Portal — per-feature tours of what you can do in the dashboard at catent.io.
- API reference — the control-plane REST API with Bearer authentication.
- SDKs — per-language guides for Node.js, Python, and Go.
A note on v1 access
Catentio v1 is single-user by design (ADR-0007 in the architecture repo). Only one Huudis identity — configured at deploy time via HUUDIS_ALLOWED_USER_ID — can sign in. Every other Huudis-authenticated user is rejected at the callback step with forbidden_user.
This is intentional. The control plane runs every agent under one principal's Anthropic OAuth and credentials. Multi-tenant Catentio (where each Huudis identity gets its own runtime) lives behind the public-SaaS provisioning track and is out of scope for this documentation.
If you're not the configured user but you want to evaluate Catentio, contact us.
A note on the Forjio family
Catentio is part of the Forjio family — a set of independent SaaS products that share identity (Huudis SSO), billing (Plugipay, for non-Plugipay products), and design conventions. If you've used Storlaunch, Fulkruma, Ripllo, LinkSnap, Pawpado, or Plugipay, the auth, envelope, and SDK shapes here will feel familiar.
Each product owns its own bounded context. Catentio owns agents, runs, projects, skills, tools, memory, and heartbeats. It does not own customer identity (that's Huudis), payment processing (Plugipay), or product storefronts (Storlaunch) — those live in their respective Forjio products.
Reach us
- GitHub issues: hachimi-cat/saas-catentio
- Email: hello@catentio.com
Ready? Go to the Quickstart.