Skip to content

Menezis Platform / Regulation

Balance in real time.

Orchestrating agent action within explicit rules.

Let’s talk architecture

01 / The principle

Agents propose the movement; rules define its limits.

Menezis Platform opens infrastructure to AI code assistants without handing them the keys. Your assistant writes a stackfile; through MCP, Menezis validates it, the Judge scores it, and the deployment runs with Docker Compose on your connected node.

Infrastructure should be invisible: you describe what must run, the rules decide what may run.

02 / The loop

From intent
to a running stack.

  1. Describe

    Your AI assistant writes the stackfile: services, parameters, resources. Nothing to configure by hand.

  2. Validate

    Menezis checks that the stackfile parses, that required fields are present, that every building block exists and that parameters pass type checks.

  3. Judge

    A mandatory Judge scores the stack with five analyzers: security (40%), policy compliance (30%), topology risk (15%), cost (10%) and operational readiness (5%). A stack with a hard-coded secret or a critical security finding is rejected and does not deploy.

  4. Deploy

    The deployment runs with Docker Compose on your connected node. It counts as successful only once the node confirms the stack is running.

03 / Invariants

What holds,
whatever changes.

01 — CHANNEL

A post-quantum channel

Between the control plane and your node agents, keys are exchanged with ML-KEM-768, the algorithm standardised in NIST FIPS 203, and traffic is encrypted with AES-256-GCM. By default, no command reaches an agent before that channel is established.

02 — PROOF

Verified, never simulated

A deployment is reported as successful only when the node confirms it. A tool that cannot act yet refuses explicitly instead of pretending to succeed.

03 — FORMATS

One stackfile, three formats

Deployments run on Docker Compose. The same stackfile can also generate Kubernetes manifests and systemd units for you to apply.

04 / The MCP toolset

16 tools.
One protocol.

The tools exposed by the Menezis MCP server to your AI assistant, grouped by role.

Stacks

validate_stack

Validate a stackfile (YAML) and return the parsing results.

generate_manifest

Generate deployment manifests for a stack (Docker Compose, Kubernetes, systemd) without deploying.

deploy_stack

Deploy a stack with Docker Compose on a connected node, after the Judge’s verdict.

get_stack_status

Get the current status of a deployed stack.

get_service_logs

Retrieve logs from deployed services.

manage_storage

Manage persistent storage volumes for deployments.

destroy_stack

Destroy a deployed stack and optionally remove its volumes.

Nodes & cloud

discover

Discover available nodes and services in the infrastructure.

get_nodes

Retrieve information about the nodes in the infrastructure.

cloud_plans

List the cloud server plans available from supported providers.

cloud_provision

Provision a new cloud server from a supported provider.

provision_and_deploy

Compose a stack, generate cloud-init and provision a cloud server in one operation.

cloud_destroy

Destroy a cloud server.

Operations & billing

billing_status

Get billing information, usage and plan details.

billing_tasks

Manage billing payment tasks: retry queue, pending list, statistics.

scheduler_control

Manage the background task scheduler: list, trigger, pause, resume, statistics.

05 / Pricing

A price per instance.
No bandwidth billing.

Flat monthly prices, excluding VAT. Add-ons extend any instance unit by unit.

Instance plans
PlanPrice / monthvCPURAMNVMe
NanoFree0.5512 MB5 GB
Micro€7.9911 GB25 GB
SmallPopular€14.9922 GB50 GB
Medium€29.9944 GB80 GB
Large€59.9988 GB160 GB
BusinessPriority supportfrom €129.99816 GB320 GB

Add-ons

Add-ons, price per unit and per month
Add-onPrice / month
+1 vCPU€4.00
+1 GB RAM€3.00
+10 GB NVMe€2.00

Nano is free and always-on, limited to one per user.

Business is a starting price, extensible with add-ons.

06 / Questions

Precise answers.

How does the MCP integration work?

MCP (Model Context Protocol) lets an AI code assistant call Menezis tools directly. The assistant writes the stackfile; Menezis validates it, the Judge scores it, and the deployment runs with Docker Compose on your connected node.

What does “post-quantum” cover?

The channel between the control plane and your node agents: ML-KEM-768 key exchange (NIST FIPS 203) and AES-256-GCM encryption. By default, the control plane sends no command to an agent until that channel is established.

What does the Judge evaluate?

Five analyzers score every stack: security (40%), policy compliance (30%), topology risk (15%), cost (10%) and operational readiness (5%). The Judge cannot be skipped, and a rejected stack does not deploy.

Which runtimes are supported?

Deployments run on Docker Compose. From the same stackfile, Menezis can also generate Kubernetes manifests and systemd units that you apply yourself.

How does the free plan work?

Nano is free: 0.5 vCPU, 512 MB of RAM and 5 GB of NVMe, always-on, limited to one per user.

When does access open?

Access to Menezis Platform is coming soon. In the meantime, write to contact@menezis.ai to talk about your architecture.