SenangAI — your data, your infrastructure, your control
Home · Agents
Sovereign AI · build agents

Built by the person who understands the work.

An agent is a name, a set of instructions, and the skills you tick. No code, no pipeline, no ticket to engineering. Pick who it is for — just you, a teamspace, or the whole organisation — and it inherits that boundary the moment it exists.

Unlimited agents · no per-agent fees · created paused

New agentScope: inherited
Who is this agent for?
Only youLegal teamspaceOrganisation
Name
Compliance Auditor
Instructions
Always cite the source policy. If unsure, say so — never guess.
Skills — what the agent can do
Search knowledge
Query graph
Redact PII
Search web
Create document
Run code
Will be created paused
TestReview & create
How it works

Instructions, skills, and a boundary.

Three decisions make an agent. Everything else — scope enforcement, citations, audit, budgets — comes from the platform and cannot be configured away.

Choose who it serves

Only you, a teamspace, or the organisation. A personal agent reads only what you yourself are permitted to see; a teamspace agent, only that space. Scope never adds access — an agent cannot hold broader permission than the space it lives in.

Scope narrows. It never grants.

Write its instructions

Tone, focus, and rules in plain language: “always cite the source policy; if unsure, say so.” Start from a template — concise analyst, step-by-step coach — or from a blank line.

Plain words, not prompt engineering.

Tick its skills

Each skill is one capability the agent may use. Unticked skills simply do not exist for it — an agent without Search web cannot reach the internet, whatever it is asked.

Capability by allow-list, not by default.
Capabilities

Everything an agent can do is something you allowed.

Agents draw on a governed library of capabilities — finding and understanding your knowledge, analysing data, producing documents and presentations, and guarding what leaves. You tick what each agent may use; everything else simply does not exist for it.

Find & understandCited answers from permitted sources, and questions answered across connections — not just keywords.
Analyse & computeData work and computation inside the boundary, never on someone else's infrastructure.
Produce & deliverSign-off-ready documents and presentations on your templates, held for approval.
Guard & delegatePersonal information detected, masked, and logged entity by entity — redaction you can show a regulator. Sub-agents run under the same scope and audit.

Capability is granted by allow-list, never by default — and every use of every capability lands on the audit trail. The full library is part of the product walkthrough.

Before anything runs

Test it, then it is born paused.

Creation is deliberately not activation. The builder ends in a test conversation, then review, and the agent arrives paused — visible, inspectable, and inert until someone with authority switches it on.

In the builder

Test before create

Talk to the agent against real, permitted knowledge before it exists for anyone else. Wrong tone, wrong skills, wrong scope — caught here, not in production.

You see its behaviour first
On creation

Born paused

The agent appears in its space with its skills, scope and instructions readable by anyone in that space. It answers nothing and runs nothing until activated.

Activation is a recorded decision
In use

Audited like everything else

Every question it answers and every skill it uses lands on the same audit trail as human activity — who asked, what was retrieved, what it cost.

One trail for people and agents
Start with one governed use case

Bring the question your organisation keeps arguing about.

Thirty minutes. We will map one use case, demonstrate scope isolation, and show the audit evidence the platform produces — or tell you plainly that you do not need us yet.