Moflet AI

For regulated environments

Production agents for environments that cannot improvise.

Moflet AI puts agents, MCP tools and cited answers over your knowledge under the same identity, authorization and audit — on cloud, VPC or air-gap.

  • pdp.allow
  • tool.mcp
  • vault.read
  • export.signed

Who it’s for

Built for environments where the data cannot leave the perimeter.

Teams in pharma, food, energy, automotive and public administration that need agents in production — and a trail that survives a security review.

Same platform. You set the perimeter: cloud, VPC or air-gap.

  • Pharma
  • Food
  • Energy
  • Automotive
  • Public administration

From question to evidence

From chat to decision, with a trail.

A question comes in through chat. The agent retrieves with citations or resolves a governed metric, pauses if confirmation is needed, runs with a trace, and leaves exportable evidence.

  1. Question
  2. retrieve / semantic_ask
  3. HITL / approval
  4. run + trace
  5. signed export

Trust

Built for teams that pass security reviews — pharma, energy, food, automotive and public administration.

Logos and case studies: coming soon

The platform

Four parts, the same control.

Agents and tools, knowledge with citations, governed decisions, and an audit you can show.

Agents and tools

Native or external agents, and the MCP tools they need, under the same identity. The model reasons; secrets stay out of its context.

Knowledge with citations

They answer over your documents and return the citation for the passage. What they claim can be opened and checked.

Governed decisions

Permission at every step, and metrics that come from your data. If a change needs confirmation, the agent stops.

Security and audit

Allow, deny and every export stay in an append-only log. The trail a security review expects to see.

The modules

A workspace, not a chatbot: modules your agents operate.

Connectors, databases, documents & files, workflows, semantics and dashboards — each with PDP, RLS and audit, and all available as agent tools.

Connectors

Catalog integrations and external MCP servers: connect over OAuth, store credentials in the vault and import their tools. Test the connection before exposing it to the agent.

Databases

Workspace tables with attributes, records and N:N relations. The tenant's structured system of record, with RLS and aggregation queries.

Documents & files

Editable documents (richtext and sheets) and files with direct-to-storage upload. Everything is indexed for retrieval with citations.

Workflows

Orchestrate deterministic and holistic steps in a persistable DAG. Durable runs with retries and checkpoints; HITL when a write needs confirmation.

Semantics

A governed catalog of terms, metrics and axioms with temporal validity. Every query signs a plan and leaves a minute tied to the run.

Dashboards

Dashboards over datasources with a governed snapshot. Share KPIs and series without exposing raw data; refresh on demand.

Why your own host

Six things the security review will ask about.

  1. 01

    The runtime is yours

    Your own host and execution. Not a wrapper over someone else's chatbot. Durable runs, per-tenant quotas, cancellation and checkpoints.

  2. 02

    True multi-tenancy

    tenant_id across the whole model, RLS and PDP. N organizations in the same database. A dedicated instance when the regulator demands physical isolation.

  3. 03

    Authorization at every boundary

    The PDP is consulted at the gateway, before invoking an agent, before every tool and before reading a credential. Least privilege, not a screen-level role.

  4. 04

    Secrets never reach the model

    Envelope encryption, per-tenant KEK, write-only. Not in the prompt, the log or the trace. Crypto-shredding when you must forget.

  5. 05

    Every decision leaves evidence

    Append-only audit, an actor on every event, signed export. There is no “trust the agent”: there is a record you can sign. With the semantic layer, every query also leaves a minute (SemanticDecision) tied to the run.

  6. 06

    The same system, air-gapped

    A portable chart. Cloud, VPC or disconnected on-prem. Self-hosted identity, telemetry with no egress. You define the perimeter.

Built to pass the review

Isolation, least privilege and non-repudiation. Out of the box.

Organizations-first identity, ReBAC at every boundary —including PDP per hop in the graph—, a vault with a per-tenant KEK, SSRF, quotas and telemetry with no egress. The semantic catalog is bi-temporal and every query leaves a minute. The same path in a trial and in a dedicated deployment.

The security model, in detail.

Deploy anywhere

The same product. You define the perimeter.

Cloud, VPC or disconnected. The API, the PDP and the audit model don't change.

Cloud

Logical isolation. One platform, N organizations. Ready to start without a cluster per customer.

Dedicated

The same chart, a single tenant. When the contract demands its own perimeter without rewriting the product.

Air-gap

No egress. Internal SMTP, self-hosted models, IdP in your network. Data doesn't leave; the audit stays.

Security, compliance and platform

See it in your perimeter

Thirty minutes. Tenant isolation, a live PDP, the vault and audit export — without handing over the data.

  • Multi-tenant architecture and dedicated instance
  • Evidence: allow/deny, hash-chain, signed export
  • Air-gap, corporate IdP, connectors under SSRF

The host. Your perimeter.
Your audit trail.

Moflet AI — the agent platform for regulated environments