Introducing Ikigenba
Published
The most direct explanation of ikigenba is that it’s a backend for AI agents, built for teams and small businesses. Don’t think of it as an agent or a “business brain” of its own. Think of it as the durable backend: the systems of record, the identity and access control, and the operational plumbing that agents need but don’t provide themselves. It presents a uniform set of tools to whatever agent you’re using via MCP.
This is what sets it apart from tools like OpenClaw or Hermes, which are themselves agents.
It’s organized into Core Services, Apps, and Connectors.
| Core Services | |
|---|---|
| Cron | Schedules events |
| Dashboard | The UI, setup instructions, and token management |
| Prompts | Triggerable prompt execution |
| Scripts | Triggerable script execution |
| Sites | Build and publish HTML content |
| Webhooks | Translate external events onto the internal event bus |
| Wiki | The knowledge base |
| Apps | |
|---|---|
| crm | Contact and customer records |
| ledger | Double-entry bookkeeping |
| Connectors | |
|---|---|
| gmail | Mailbox access and email events |
| dropbox | One-way mirror of a Dropbox folder |
| ntfy | Push notifications |
| github | Reserved, not yet built |