Ecosystem

The oc8 ecosystem.

Everything you install in oc8 is a Capa. An agent template, an MCP tool pack, a guardrail set, a department template, a runtime, or a bundle of several.

oc8 octopus mascot
Capas

Pick a Capa.

Lead Enrichment

Agent · Sales · HubSpot

Looks up new contacts, fills in the missing fields and writes them back to the CRM.

Lead Scoring

Agent · Sales · HubSpot

Scores inbound leads against your own criteria and flags the ones worth a call.

Quote Writer

Agent · Sales · Odoo

Builds a quote from the deal and sends it once you approve.

Deal Handoff

Agent · Sales · HubSpot + Odoo

Moves a won deal into Odoo as a project or an order, without retyping.

Ad Creative

Agent · Marketing · Higgsfield

Builds paid social creative from a product shot, in variants per placement rather than one generic image.

UGC Video

Agent · Marketing · Higgsfield

Produces creator-style vertical video with a presenter and a voiceover, cut for short-form feeds.

Social Composer

Agent · Marketing · Higgsfield

Puts the post together: the caption, the matching asset, and the channel it is cut for.

Ticket Triage

Agent · Support · Jira

Reads new tickets, categorizes them and drafts the first reply.

Order Status

Agent · Support · Odoo

Answers where an order stands by checking the order, the delivery and the invoice.

Approval Inbox

Agent · Internal · Slack

Brings approvals to where the team already works, and records the decision.

Cross-System Answers

Agent · Internal · Slack + all

Answers a question in Slack by looking in every connected system at once.

Daily Digest

Agent · Internal · Slack

Posts what the agents did overnight, what is waiting for a person, and what failed.

Connectors

Any system.

Agents reach their systems through the same open protocol, so one connection carries many agents instead of every agent needing its own.

Odoo
ERP
HubSpot
CRM
Microsoft 365
Productivity
Slack
Internal
Jira
Support
GitHub
Code
Higgsfield.ai
Marketing
+ More to come
build or ask
Models

Any model.

The agent describes what it needs. Which model runs it is a setting, not part of the agent.

Per agent, not per company

Ticket triage does not need the model that writes your quotes. Each agent gets its own, so you spend where it matters.

Swap without rebuilding

Change the model tomorrow and the agent stays as it is. Nothing to migrate, nothing to rewrite.

Wherever it runs

A cloud provider, your own hardware, or infrastructure inside the EU.

Build

oc8 is made to build.

Run it locally, try it out, build an agent. You will know quickly whether it fits the way your company works.

When you get stuck, come to us or ask the community. That exchange is where the useful things come from: someone connects a system nobody had touched, someone else finds a better way to handle approvals, and the next person starts from there instead of from scratch.

That is what we are building, and there is room in it.

Services

Where to start.

1

AI enablement

Work out where agents belong in your company, and where they do not. Governance, risk classes and the EU AI Act obligations that apply to you, before anything is built.

2

Agent development

Build the agents and connectors your case needs, including systems nobody has covered yet.

3

Implementation

Roll oc8 out across teams and systems, with the approval rules and audit trail your compliance people ask for.

Start where it makes sense.

Try it yourself, or bring us the process you want to automate first.