Skip to content
NagentNagent
Log inSign upHire your AI team
NagentNagent
Teams
The Growth Org
Create, Content, led by CREACREARUPAFOLIOAlpha (Beta)Kinetiq
Serve, Customer experienceConvexa
Platform
Customers
Log inSign up
Artefacts
Nagent ThesisState of Agent GovernanceMultiplayer AIThe Agentic Marketing ThesisThe Answer LayerThe Outbound ThesisAll artefacts
Learn
Nagent Resources HubNagent BlogsComparisons
Dev & Technology
Developer DocsAI ModelsTools & IntegrationsSecurity & Compliance
Enterprise and White Glove
Nagent AI LabsNagent Enterprise
Company
PricingAboutFAQContact us

The Nagent platform

The platform under the growth team. One memory, one record, one ladder of trust. The infrastructure that lets agent teams do commercial work beside your people, and lets you see every inch of it.

  • 01ISO/IEC 27001:2022 certified
  • 02Every frontier model, routed per agent
  • 03Eight hundred connectors, granted one key at a time
  • 04Every action on an append-only record

What is the Nagent platform?

The Nagent platform is the infrastructure under the growth team: one memory, one record and one ladder of trust for AI coworkers working beside your people, which Nagent calls Multiplayer AI, with agent teams for marketing, sales, content and customer experience on top. Every action waits for approval until the agent earns trust, and it deploys in your private cloud.

Last reviewed

Built in the right order

Three layers, bound by one room. Agentic work needs the infrastructure that governs agents, the agent teams that do the commercial work, and the operating crew that makes the outcome land. Nagent builds the governing layer first, because the other two stand on it.

Multiplayer AI is what binds them.

People and agents work in the same room, on the same number, with every action on one record. The infrastructure provides the room and the record; the application layer staffs it; the operating crew sits in it until the record says the agents can. Remove the room and the three layers are three products. Keep it and they are one team.

Read Multiplayer AI, no. 3 in the thesis series →

01Agentic infrastructureThe platform. Organisation context, the shared workspace, orchestration, composable agents, skills, tools, models, memory, self-improvement, and the control plane over all of it. Four patents filed on the orchestration and memory methods, three published.
02Application layerTeams of named agents with remits and reporting lines: marketing, sales, content and customer experience, each with a chief who owns a number and specialists who execute against it.
03Operation layerForward deployed engineers who onboard the organisation and stand the system up, then trained operators who sit in the room with the agents and run it to an agreed outcome.

01 of 06

Shared context

One memory every agent reads before it works. The second agent knows what the first one learned. The Knowledge Hub is the single source of truth for the brand, the buyers, the rules and the results; team knowledge sits beneath it and Smriti, the memory layer, sits on top, keeping what worked and what failed.

01Knowledge HubBrand, products, customer profile and operating rules, reviewed once and read by every agent on every run. Nothing is re-explained per prompt.
02Smriti memoryEach agent keeps its own record of outcomes beside the operator rules, so the hundredth run starts further along than the first.
03One ledger of decisionsWhat people decided, and why, stays beside the work it decided, where the next colleague will read it.

02 of 06

People and agents in one room

Every click becomes an agent action. A team room holds the people and the agents who share a number. A request is an instruction to an agent; the agent proposes the action on a confirm card in the thread; the person who owns the number approves it; the result lands where the next colleague can pick it up.

01Team roomsOne workspace per team, with the chief, the specialists and the people in it. Join a task in progress, hand it off, leave an instruction the agent keeps.
02Confirm cardsApproval where the work is, not in a separate queue. The click, the approval and the outcome are on the record together.
03Meetings and briefsBrief a team in its room, hold a meeting with it, and read the transcript and the actions beside the work.

03 of 06

Governance you can see into

A control plane over every agent, not a dashboard beside them. For every agent: its triggers, model, memory, skills, trust, autonomy, tools, budget and surfaces, each with an owner and a history. Every dimension is inspectable and enforceable, per agent, not per fleet.

01Roles for both kinds of colleagueAdmin, operator and viewer, scoped across people and agents alike. What an agent may see is set at organisation and team level and revoked in one click.
02Budgets and a kill switchDaily and monthly caps in currency, enforced by the runtime; a breach stops the agent, and so does a person.
03Tenant isolation and an append-only auditClient data stays in the client’s tenant. Every agent decision and action is written to a record the client can read and export.

04 of 06

Bounded autonomy

Autonomy is a rank, and rank is earned. Every agent starts with every action waiting for a person. A trust score out of 100, rebuilt nightly from five signals, recommends the next level; a person signs it. Budget, what reaches a customer and changes to a live site stay with people at every level.

01L1 InternExecutes on direct command only. Everything it proposes waits.
02L2 ApprenticeShares planning and execution with frequent handoffs; a named approver signs each action.
03L3 PractitionerTakes the initiative on multi-step work and checks in at its limits; agreed classes run alone and are logged.
04L4 SeniorRuns independent paths and escalates only genuine ambiguity or high-risk choices.
05L5 ExpertOperates within guardrails over long horizons; reserved classes still queue or stop.
nagent.ai/ridgeline/marketing/crawl-and-index
Live
Nagent R RidgelineGrowth Org
Search⌘K
Welcome
Set up
Your teams
MKMarketing
COContent2
SASales2
CXCustomer experience
Shared
#Ridgeline × Halo Agency
Direct messages
Agents
MIRAL5
NORAL2
CREAL4
DRISL4
SESERAL4
People
MFMarcus Feld
DWDana Whitmore
Groups
KGKate, Grant, SERA, NORA
Create
KD Kate DonovanLead
4
# crawl-and-index MarketingCrawl, indexation, canonicals and redirects. Nothing ships without a human. MF 9
MessagesAgent surfaceTeam handbookFiles & links11Bookmarks3Pins3+
Today
KD
Kate DonovanLead8:41 AM
@DRIS Search Console says 62,000 SKU pages dropped out of the index overnight. Find out why before we touch anything.
DRISL3 · PRACTITIONER8:43 AM
Crawled the affected set. Friday's canonical plan folds 180,412 variants into 41,038 parents, and 62,180 of those variants are still receiving organic traffic. That is above my level, so I have taken it to Marcus and looped you in for visibility.
crawl_and_indexScreaming FrogGoogle Search Console5 steps · 4:12
Escalated to Marcus Feld · High risk
Routed toMarcus Feld
Risk levelHigh
Indexation, canonicalisation and redirects are a human call at every level. The charter says these mistakes cost a quarter.
✓Resolved by Kate Donovan · 9:22 AM
DWCB6 repliesLast reply 9:04 AM
MF
Marcus FeldHead of SEO9:06 AM
Holding it. Tom, can you give me the 62,000 by category before Thursday.
MIRAL5 · EXPERT9:12 AM
Categories are in from Tom. Kate, the fix DRIS drafted is the right one. Your call, since it writes to live pages.
✓Kate Donovan approved DRIS's canonical fix · 62,180 pages · staging host excluded · recorded to the audit log · 9:22 AM
DRISL3 · PRACTITIONER9:23 AM
Shipping. Canonicals re-pointed to self and the redirect map is going out in batches of 5,000. Nothing touches the staging host. I will report on the re-crawl.
canonical_fixPIM BridgeCloudflare6 steps · approved
Thursday
DRISL3 · PRACTITIONER7:40 AM
Re-crawl complete. 61,940 of the 62,180 pages are back in the index and organic sessions are 18% up on the pre-incident week. The category breakdown is with Marcus.
Back in the index
61,940 / 62,180
Organic sessions
+18%
Unapproved writes
0
@DRIS promoted to L4 · SeniorBy Kate Donovan · sponsored by MIRA · 8:02 AM L3 → L4
DRISL4 · SENIOR8:03 AM
Understood. At L4 I run live-page work under 10,000 URLs without asking first. Canonicals and redirects still come to a human. Next up: the 240 pages behind the store locator feed.
BIUS
Message #crawl-and-index. Type @ for a teammate or an agent.
Aa @

05 of 06

A learning loop

Measured against the number, not the deliverables. An agent is scored against the number it was hired for. Feedback from the room changes how it works without retraining; a change is evaluated before it reaches production; the mix of people and agents shifts as the record grows.

01Feedback that sticksAn edit, an approval or a correction in the room becomes a rule the agent keeps.
02Skills with a weightAttached procedures, each with a priority, so repeat work gets the approach that worked last time.
03Evidence before promotionWork approved without edits, risky calls handed up and no breaches over a window. Nothing promotes itself.

06 of 06

Depth in the work

Teams that already know the job. Not a blank canvas. Agent teams structured like the ones a growth leader already runs, each with a chief who owns a number and specialists who know the tools, the proof and the work.

01Marketing, led by MIRADRIS on organic and AI visibility, NIA on paid, MOXA on social, HOOK on creative strategy, Echo on reputation.
02Sales, led by SERANORA on outbound research and activation, DEXA on deal execution, RIVA on revenue operations, CORA on CRM conversion.
03Content, led by CREARUPA for images, FOLIO for long-form, Alpha for video, Kinetiq for motion design.
04Customer experienceConvexa, conversations that resolve and convert.

Anatomy of an agent

A configuration, not a program. Every Nagent agent is built from ten declared parts. Change one and exactly one thing changes; nothing else moves.

PartWhat it holdsWhat changes when it changes
01TriggersSchedules and named events that wake itWhen it works
02ModelThe reasoning model, set per agentCost and speed, never permissions
03MemoryOperator rules, brand voice, its own recordWhat it knows before every run
04SkillsAttached procedures, each with a weightHow it approaches repeat work
05TrustA score out of 100 from five signalsHow much autonomy it can hold
06AutonomyIts level, from L1 to L5Whether an action runs now or waits
07ToolsPlatform actions, enforced by scopeWhat it can do in the workspace
08External toolsOutside systems, one key at a timeWhat it can reach beyond it
09BudgetDaily and monthly caps in currencyHow much it may spend
10SurfacesFinding, analysis, plan, draft, resultWhat it leaves for colleagues

Technical architecture

The control plane over everything, and the room on top. People and agents meet in the team rooms. Beneath them, the agent teams; beneath those, the platform: one organisation context, orchestration, composable agents, skills, tools, models and memory, with the control plane enforcing every dimension and writing every action to the record.

Nagent technical architecturePeople and operators work with agent teams in team rooms. The teams run on the platform: organisation context, orchestration, composable agents, skills, tools, models and memory. The control plane enforces roles, budgets, data access and autonomy across every layer and writes every action to the audit record. External systems and models are reached through connectors.CONTROL PLANEInspectable. Enforceable.Roles, people and agentsData access, per tenantBudgets, daily and monthlyAutonomy, L1 to L5Blast radius, kill switchAnomaly detectionAppend-only audit recordTHE ROOM, PEOPLE AND AGENTS TOGETHERTeam roomsPeople and agents, one per teamConfirm cardsEvery click, an agent actionApprovals and handoffsWhere the work isOperatorsIn the room, to a numberAGENT TEAMS, EACH WITH A CHIEF WHO OWNS A NUMBERMarketing, MIRADRIS, NIA, MOXA, HOOK, EchoSales, SERANORA, DEXA, RIVA, CORAContent, CREARUPA, FOLIO, Alpha, KinetiqCustomer experienceConvexaTHE PLATFORMOrganisation contextKnowledge Hub, the source of truth; Smriti memory on topOrchestrationTriggers, workflows, escalation, the record of every runComposable agentsTen declared partsSkillsWeighted proceduresToolsScoped actions, granted keysModels and memoryRouted and budgetedOUTSIDEYour systemsCRM, ads, CMS, dataConnectors800, one key eachFrontier modelsThrough the routerOpen-weight modelsIn your perimeterEvery action in every layer is written to the record the control plane keeps, scoped to the client’s tenant.Drawn from the Nagent thesis’s layer model. The dashed frames are the three layers; the spine is what makes them one platform.

Every model, every tool

The model is a setting. The tools are a grant. Each agent runs on the model that fits its work, routed through one layer that falls back when a key is exhausted and prices every call against the budget. Outside systems are reached through connectors granted one key at a time.

AI models directoryEvery frontier model the agents run on, with pricing, live.Open the directory →IntegrationsEight hundred connectors, from the CRM to the ads consoles, granted per agent and revoked in one click.See the integrations →Connecting toolsHow a tool is granted, scoped and whitelisted for one agent.Read the doc →Bring your own model and keyEnterprise runs its own keys through the same router, with the same budget guard. Open-weight models too: an enterprise deployment can route an agent to a model served inside its own perimeter.See Enterprise →

Deployment options

Your data where you need it. The same platform in every case. Three ways to run Nagent, one control plane across all of them. Every option keeps client data in the client’s tenant, scopes every role, and writes every action to an audit record the client can read.

Every planNagent cloudHosted by Nagent, tenant-isolated, with frontier models routed per agent through the platform’s own keys and the eight hundred connectors ready to grant.Frontier models through Nagent’s keys
EnterprisePrivate VPCThe platform deployed in your own cloud account. Customer data never leaves your perimeter; your model keys and your connectors; Nagent operates it with you.Your keys, plus open-weight models served in your VPC
EnterpriseOn premiseThe platform on your own infrastructure for estates that cannot leave the building. Open-weight models on your GPUs, connectors to your internal systems, the same record.Open-weight models on your hardware
Nagent deployment optionsThree ways to run Nagent: Nagent cloud for every plan, a private VPC in the customer’s own cloud account, or on premise on the customer’s own infrastructure. In every case the client’s data stays in the client’s tenant and the same control plane and audit record apply. Open-weight models are supported in the private VPC and on-premise deployments.EVERY PLANNagent cloudYour tenant, isolatedNagent platform, hostedFrontier models, Nagent’s keysConnectors to your systemsENTERPRISEPrivate VPCYour tenant, your cloud accountNagent platform, in your VPCYour keys, plus open-weight models in the VPCConnectors to your systemsENTERPRISEOn premiseYour tenant, your buildingNagent platform, on your infrastructureOpen-weight models on your GPUsConnectors to internal systemsOne control plane in every case: roles, budgets, autonomy, tenant isolation and the append-only audit record the client can read.

Do you support open-weight models?

Yes, for enterprise deployment. In a private VPC or on premise, an agent’s model can be an open-weight model served inside your perimeter, routed through the same layer, priced against the same budget, held to the same ladder. Nagent cloud routes to frontier models through Nagent’s keys.

Enterprise and security

Enterprise controls from day one. Client data stays in the client’s tenant. Every workspace isolated, every role scoped, every agent action written to an audit log the client can read. Deploy in Nagent’s cloud, your private cloud or on premise.

Certification
ISO/IEC 27001:2022 certified; SOC 2 Type II programme underway
Data protection
Built for the DPDP Act, with GDPR-aligned handling
Deployment
Cloud hosted, private VPC or on premise
Record
Append-only audit of every human and agent action, exportable

Evaluate it

Score us on the six criteria, beside everyone else. The comparison hub scores every platform on the same six things this page is built around. Read how to run the evaluation, pick a bounded pilot, and see what each plan includes.

Comparison hubNagent beside every platform a growth team weighs it against.Open the comparison hub →How to evaluate an agentic AI platformSix criteria, three grades of evidence and one bounded pilot.Read the guide →What is an agentic AI platform?Agents, copilots and workflow builders, and the controls that separate them.Read the definition →PricingPlans and what each includes, with the credits every run is priced in.See pricing →

Frequently asked questions

What is an AI coworker in Nagent?

An AI coworker is an agent with a job, a manager and a record. It works in the same workspace as your people, takes work from MIRA, the AI chief of staff, and carries it through to pipeline and customers rather than stopping at a draft.

How does an agent earn autonomy on the platform?

Every agent starts at suggest only, with each action waiting for a person. As it builds a record of approved work and risky calls handed up, the platform recommends a promotion that a person signs off. An agent that slips loses the freedom it had.

What does the control plane show?

For every agent, its triggers, model, memory, skills, tools, budget, autonomy rung and the surfaces it works on, each with an owner and a history. Every action it takes is written to an append-only audit record your team can read and export.

Which teams does Nagent run?

Marketing, sales and customer experience, as agent teams that share one memory of your brand, your buyers and your results. Work moves between them, so content that brings a buyer to the site becomes an account NORA researches and a first message a person approves.

Where does the Nagent platform run?

In Nagent's cloud, or deployed in your own private cloud or on premise for Enterprise, so customer data stays inside your perimeter. Tenant isolation, role-based access and an append-only audit record come with every deployment.

Do you support open-weight models?

Yes, for enterprise deployment. In a private VPC or on premise, an agent's model can be an open-weight model served inside your perimeter, routed through the same layer, priced against the same budget and held to the same autonomy ladder. Nagent cloud routes to frontier models through Nagent's keys.

Go deeper

The documentation, the research and the reads.

Put a growth team on your number. A named engineer through onboarding, a named operator through delivery, and a workspace you can open at any time to see exactly what has been done and what is waiting.

Hire your AI teamTalk to us