The Agent Operations Layer

Onboard your AI agents the way you onboard people.

Every new colleague gets an induction, an access badge and a manager who signs off their first work.

Meshly gives your AI agents the same start: they learn what your data means, they reach exactly the data they are allowed to use, and their work is signed off before it lands, by a person by default. Your agents then build your software and run your processes on your own data, with the rules enforced by the platform on infrastructure you choose.

SYSTEM / AGENT OPERATIONS LAYER4 LAYERS

Four layers, from top to bottom. Meshly Build is highlighted.

  • 4 · Agents and modelsCoding · Process · Local · CLIReplaceable workers, from any vendor.
  • 3 · Meshly Build (highlighted)Rules · Review · RecordNo agent approves its own work.
  • 2 · Meshly Data StackYour data · Meaning · PermissionAgents see only what they are allowed to.
  • 1 · Your infrastructureOn-prem · Private cloud · Airgapped
Every agent passes through one layer, which Meshly hosts or you run yourself.FIG. 1
MeaningPermissionProofHosted or self-hosted

A new category

Every agent needs one layer to pass through, and we built it.

The agent market is splitting into pieces, and each vendor sells one of them. What every company still needs is the place where an agent’s work becomes something it can trust. We call that place the Agent Operations Layer, and that is what Meshly is.

PieceWhat it doesWhat it leaves out
OrchestrationWhat it does: It runs agents in parallel.What it leaves out: Every model vendor is building it into its own tools, so it is fast becoming a free feature.
ContextWhat it does: It feeds agents information.What it leaves out: It tells an agent what it could know, and it leaves open what the agent is allowed to do.
Model hostingWhat it does: It serves the models.What it leaves out: It makes inference available and leaves the data and the rules to you.
Agents as a serviceWhat it does: It rents you a workforce.What it leaves out: The workforce runs on someone else’s platform, with their data handling and their terms.
The Agent Operations LayerWhat it does: It gives every agent meaning, permission and proof.What it leaves out: It runs beside the agents and models you choose, hosted by Meshly or on your own infrastructure.

From pilot to workforce

Agents do real work once they get what every new colleague gets.

An agent that knows what your data means gives the right figure the first time. An agent that works inside enforced rules can take on real processes, and an agent whose every step is on record can move from the pilot into production.

Today’s models are already good enough for this work. Meaning, permission and proof turn them into a workforce, in the same way that an induction, a badge and a manager turn a new hire into a trusted colleague.

The layer

Every agent needs three things before it can do real work.

The platform provides and enforces all three, so every agent gets them on every task.

1

Your agents know what your data means.

Meaning

Metadata, lineage and quality live in the data layer, and decisions and conventions live in shared project knowledge. Agents start every task from facts.

2

The server enforces every permission.

Permission

In Meshly Build, the server checks access levels and approval gates on every board action, so every rule holds whatever a prompt says. In Meshly Data Stack, every request carries two credentials, one for the person who asks and one for the agent itself. Keycloak and OPA policies use both to decide which data the answer may use and whether each field comes back in full, masked or empty, and Superset applies row-level security on top of Trino.

3

Everything is on record.

Proof

Every task, approval, token and cost is recorded against the agent and the person who approved it. The record is ready for an audit from the first commit to the last process step.

One rulebook

Agents that build and agents that run follow the same rules.

One layer governs the agents that write your systems and the agents that run your business, so you keep one rulebook and one record.

1
Agents that build

Meshly Build

Hosted by default · Self-hosted option

Meshly Build turns AI coding agents into an accountable engineering team. It gives them roles, approval gates, shared knowledge and cost control, and it attaches evidence to every change.

Explore Build
2
Agents that run

Meshly Data Stack

Self-hosted · Consultation-led

Meshly Data Stack is the data layer your agents work on. Meaning, lineage and access rules live with the data, on infrastructure you control, and every deployment starts with a conversation.

Explore Data Stack
3
Agents that think locally

Meshly CLI

Local LLM · Your network

Meshly CLI is a coding agent in your terminal, and it runs on a model you host yourself. With the Meshly AI appliance, the whole loop stays on your own hardware.

Explore CLI

In production

Agents are already doing real work.

They work in software delivery, on data platforms and in regulated processes, always on the customer’s own data and in the customer’s own environment. We deliver with Meshly partners, and we keep our customers’ names confidential.

1

One developer now leads a team of governed agents.

Retail · Software delivery · Measured

One developer built a customer-facing application with Meshly Build agents. The team merged 376 pull requests and 40,000 lines of production code in 23 working days, and each shipped feature took less than one hour of human work.

2

A cloud warehouse was replaced, and the data stayed at home.

Financial services · Data platform · In production

A financial services company moved from a metered cloud data warehouse to Meshly Data Stack in its own environment, and it now pays one flat annual price.

3

Agents prepare the regulatory reporting.

Insurance · Process agents · In delivery

Agents assemble the own risk and solvency assessment (ORSA) from the insurer’s own data. Actuaries review and approve the result, and every step and every data access is on record.

4

Security compliance keeps itself up to date.

Critical infrastructure · Security · Pilot

Agents collect security audit evidence and keep it current against national security requirements. They work in an isolated environment and under the organisation’s own rules.

We build every Meshly product on Meshly Build. Across the whole Meshly workspace we estimate 12,694 tasks completed, 2,403 agent hours and 500+ releases across 40+ projects, as of November 2026. See the record

On your ground

Meshly runs where you decide.

  1. You choose the ground. You choose between your own data centre, a private cloud and a fully airgapped network. Meshly Data Stack is built for Red Hat OpenShift in your environment, so it needs no hyperscaler, and self-hosted Meshly Build runs on your own servers. Meshly hosts Build by default for teams that prefer to skip the operations.

  2. Your keys, your models and your logs stay with you. When the platform runs on your own infrastructure with local models, everything stays inside your environment, and no telemetry calls home. Meshly CLI drives its agents with local models, so your own hardware does all the inference. Build’s Station agents run Claude Code or Codex, and those tools call their vendors’ APIs.

  3. Your costs stay predictable. Meshly Data Stack has one flat annual price that covers every query, every seat and every terabyte. When you run local models on your own hardware, there is no per-token bill.

  4. You can always leave cleanly. We provide a software bill of materials for the release you run and source-code escrow on request, and your data stays in open formats.

One level deeper

Good decisions need detail.

The Trust Center describes the security practices of each product, the independent review behind them and how you report a vulnerability.

Open the Trust Center

Risk and compliance

Compliance is built into how the layer works.

On the Meshly Build board, every agent action needs a permission and leaves a log entry. In Meshly Data Stack, policies weigh both the person and the agent before any data moves. Regulators ask for exactly these controls, and your auditors can check them.

RegulationTopicHow the layer answers it
DORATopic: ICT third-party risk · Exit strategyHow the layer answers it: Meshly Data Stack, and Meshly Build when you self-host it, run in your own environment instead of a vendor cloud. Source-code escrow is available on request, and open data formats give you a documented exit at any time.
NIS2Topic: Supply-chain securityHow the layer answers it: We provide a software bill of materials for the release you run on request, for your supplier assessment. Every review in Meshly Build includes a security scan with an exportable evidence record.
EU AI Act · Art. 12Topic: Record-keepingHow the layer answers it: Meshly Build logs every agent action on the board, including which agent acted, what it changed, which gate it passed and who approved the result.
GDPRTopic: Data minimisation · ResidencyHow the layer answers it: With Meshly Data Stack, personal data stays in your environment. Keycloak single sign-on and OPA policies decide what each person and each agent can see, Trino masks fields through those policies, Superset applies row-level security, and access is logged.
National securityTopic: Airgapped deliveryHow the layer answers it: Airgapped deployment, local models and a dedicated delivery path serve environments that cannot connect to the internet.

Ways to work with Meshly

You can build it yourself, have it built, or do both.

  1. Direct, for organisations with their own engineering team. Your developers build with Meshly Build and run agents on your own Data Stack. We provide the platform, architecture support and a direct line to the people who built it. Book a conversation

  2. Through a partner, for organisations that want it delivered. A Meshly partner designs, builds and runs your agents and data on the platform, and brings industry knowledge and local delivery. Ask about partners

  3. Both, with your team leading and partners scaling. You start direct and bring in a partner when you need more hands or deeper industry knowledge.

The platform and the rules stay the same whoever does the work, and you stay free to change the mix at any time.

Become a Meshly partner

Request

The Agent Operations Layer

Let’s onboard your first agent together.

Tell us about your team and one process you want agents to run. We reply within two working days with a proposal for a working session.

Or write to hello@meshly.fi