Platform
A visual platform on top, real files underneath.
Noro runs on proprietary software built for operating AI agents as a service. Staff work in the interface; engineers work in the files; both edit the same thing.
Two layers
Layer 1 is what you see. Layer 2 is why it can be tailored.
An agency with its own software — not a self-service automation tool. The visual layer is designed to cover the common work; the developer layer covers everything specific to one business. The platform is built out in stages, so the list below is scope, not a feature inventory — at scoping we say which parts your engagement uses from day one.
Layer 1
Visual platform
Designed to cover:
- CRM: contacts, companies, leads, deals, tasks
- Client workspaces with enabled modules only
- Agents, their brain files and organisation graph
- Knowledge collections and document indexing
- Model registry, usage and cost per client
- Tools, integrations and permissions
- Workflows with visible run logs
- Client dashboards, bills and reports
Layer 2
Developer access
Designed to cover:
- Agent folders as real files on the server
- Custom tools and integrations in code
- Advanced workflows beyond the visual builder
- Server configuration and deployment
- Editing over SSH — changes are picked up by the platform
- Claude Code as a first-class way to maintain agents
Agents as files
An agent is a folder. The interface is a view of it.
Instructions, knowledge, tools, models, memory and relationships each live in their own file. Edit them in the platform or over SSH with Claude Code; the platform is designed to pick the change up and reindex it.
clients/<client>/agents/sales-agent/
- agent.yaml
- instructions.md
- knowledge.yaml
- tools.yaml
- models.yaml
- memory.yaml
- relationships.yaml
Designed to validate before every save, so a broken file cannot replace a running version.
Screens
What the platform looks like.
Screenshots of the running platform, filled with the demo workspaces we build against — never a customer’s data or figures. Where a part of the platform is still being built, you get a labelled preview instead of a photograph of something that does not exist.
Agent Brain — the agent’s instructions file, edited in the platform and on disk.Screenshot of the Noro platform with demo data Agent organisation — who supervises, delegates to and reports to whom.Screenshot of the Noro platform with demo data Knowledge — collections as folders, documents indexed for retrieval.Screenshot of the Noro platform with demo data Workflow builder — triggers, agents and approvals as one runnable graph.Screenshot of the Noro platform with demo data Usage — model calls, tokens and billable usage per client, agent and model.Screenshot of the Noro platform with demo data Proposal builder — blocks on the left, the live proposal page on the right.Screenshot of the Noro platform with demo data Client portal — what a client sees: their own workspace, read-only.Screenshot of the Noro platform with demo data The same client portal on a phone.Screenshot of the Noro platform with demo data
Isolation and access
Built for many clients, isolated for each.
Isolated workspaces
Every client’s records, agents, documents and usage are separated at the database level and tested for it.
Credentials per client
Keys to your systems are stored encrypted, scoped to your workspace, and never shown in full.
Read-only client access
Your login shows what runs, what it did and what it costs. Operating the agents stays with Noro.
Invitation only
There is no public sign-up. Access is created by Noro staff for the people you name.