The same plane and the same published key as every plan, with allowances, seats and retention sized to you, and support terms and paperwork agreed per contract. This page answers what security, legal and procurement teams ask first, and says where a document is not yet published.
Entity: order formLaw: set in order form
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
© 2026 Intramedial. All rights reserved. Intramedial is a product by Trustvice. Secured and supercharged by Avonao Labs.
Report abuseTeam and Scale include single sign-on and auditor access, set up through Avonao ID. Enterprise changes the commercial and contractual layer: sizes, terms, commitments and support, each agreed per contract. It will be stated in the order form too.
| Item | Team and Scale (self-serve) | Enterprise |
|---|---|---|
| Monthly allowances | Fixed per plan, with action packs | Custom, configured per contract |
Tell us your volumes, regions and requirements. A person replies within one business day.
| Seats |
|---|
| Team 5, Scale 15 included; extra seats bought in Billing |
| No fixed seat limit |
| Ledger retention | Team 90 days, Scale 180 days, per plan. | Custom, agreed in your contract; nothing is deleted automatically unless the contract says so |
|---|
| Uptime | No uptime commitment on self-serve plans | At least 99.9% monthly uptime under the Enterprise SLA, with service credits |
|---|
| Support | Team 8h response on business days, Scale 4h on seven days | Dedicated support, agreed per contract, with response targets written down |
|---|
| Terms | Terms of Service, accepted online | A signed order form, which prevails over the Terms where it says so |
|---|
| Billing | Card through Avonao Billing, see pricing page | Quoted per contract, with invoicing and purchase orders on terms agreed per contract |
|---|
| Single sign-on via Avonao ID | Team and Scale plans | Included in the order |
|---|
| Data regions | Per workspace | Per workspace |
|---|
| SCIM directory provisioning | Not offered | Planned later |
|---|
Allowances, seats, retention and terms are agreed per contract, so this page quotes no Enterprise price. The self-serve plans and their prices are on the pricing page. Compare every plan →
A neutral middle is only useful if every customer gets the same one. Enterprise buys capacity, terms and support. It does not buy a different kind of decision.
Intralock is the same pure function on every plan. Enterprise buys capacity and terms, and unlocks no hidden kernel.
A Merkle root with an Ed25519 signature, the same envelope as every ledger bundle.
Bundles are signed with the key for the workspace’s jurisdiction and published at one address, so your auditors verify them like anyone else’s.
A bundle stays verifiable offline with the published public key, whether or not the service is available. Keep the key next to the bundles and they verify on their own, years later.
A bundle proves that it was signed with an Intramedial key and that nothing in the range it seals has changed since. It seals the audit log, a separate trail from the coordination ledger, and it does not show that anything an agent declared was true. Verification is offline, against the published key. What a module does not do →
The Enterprise SLA covers the API at api.intramedial.com and the MCP server at mcp.intramedial.com and takes effect with a signed order form: at least 99.9% monthly uptime, with service credits when a month falls short.
| Monthly uptime | Credit on the monthly fee |
|---|---|
| Below 99.9%, at least 99.0% | 10% |
| Below 99.0%, at least 95.0% | 25% |
| Below 95.0% | 50% |
Credits, caps and the claim window are not defined yet. Nothing here is a commitment; any credit exists only if your order form says so.
| Severity | Acknowledged |
|---|---|
| Severity 1The service is unavailable for your production use, or admissions cannot be decided. | Within 1 business hour |
| Severity 2A major feature is impaired or the service is degraded, and a workaround exists. | Within 4 business hours |
| Severity 3A minor problem, a question or a request for information. | Within 1 business day |
Support is staffed during business hours, as the Enterprise SLA defines them. Enterprise requests are acknowledged within 1 business hour (Severity 1), 4 business hours (Severity 2) or 1 business day (Severity 3); the time counts from receipt, or from when business hours next begin for a request that arrives outside them. These are acknowledgement targets: a person confirms they are working on it. They are not resolution targets.
Which checks count as downtime, how a minute is counted, which events are excluded and how a credit is claimed are open points. They will be written into the SLA and the order form. Nothing on this page should be read as a commitment about any of them, and no failed check is promised to count as downtime. Ask us what you need. The documents are being revised for Intramedial.
Planned maintenance, customer-caused errors, force majeure, test usage, beta features and third-party destinations are the kinds of exclusion an SLA usually lists. None is defined for Intramedial yet.
A right to leave after repeated misses is a usual SLA term. Whether, and at what level, it applies here is not decided yet, so none is promised.
Whether incidents are posted to the status page, and whether notices are sent by email, is not yet stated. The status page shows what is checked.
The architecture and module behaviour are public, so a reviewer can start before the first call. Some documents are being revised.
A page for controls and legal documents, under revision. Ask us for what you need.
/trust →Module docsRequest, response, errors and the adoption stage each module honours, from observe to enforce.
/docs/modules →SecurityThe security overview, with the vulnerability report form and the way to reach the security team.
/security →Signing keysOne key per jurisdiction, published at a well-known address. Where the keys are held is not yet published.
/docs/ledger-bundles-snapshot →| Item | State | Detail |
|---|---|---|
| Security questionnaire | Ask us now | Written answers to a reasonable questionnaire within 30 days, under DPA section 9. |
| Customer audit | Ask us now | Customer audit terms are not defined yet. Tell us what you need and we will say what we can offer, and on what notice. Ask us if you need it sooner. |
| Sub-processor compliance reports | Ask us now |
Each workspace is created in the data region you pick, and its data is stored there. Scheduled jobs, counters and the ledger run in the zone of that region, with a copy of each worker in every zone, not in one place. It will be stated in the order form too.
For procurement
wnam · USweur-1 · EUapac · APACoc · OCEurope stores data under Cloudflare’s EU jurisdiction, which Cloudflare enforces, for the database and for object storage.
Asia-Pacific and Oceania are location hints, not guarantees. Compute runs at the nearest edge unless a contract adds Regional Services.
A few Cloudflare services cannot be pinned, such as KV, Queues and Workers AI. Customer content is kept out of them.
The Data Processing Addendum and the privacy policy are being revised for Intramedial. Until they are published, this page states nothing about their content, and you should not rely on any of it.
The roles of the parties are set in the DPA, which is being revised. They are not restated here.
Transfer mechanisms for Intramedial are not yet published. They will be named in the DPA, and in the order form where it differs.
The account owner is told without undue delay and in any case within 72 hours of us becoming aware of a personal data breach.
How changes to the provider list are announced is not yet published, nor whether you can object to a change. Ask us if you need it sooner.
Return and deletion terms for Intramedial are not yet published. Ask us before you rely on a period or a method, and get it in writing.
Named Article 27 representative in the European Union.
Which document prevails when an order form and the DPA differ will be stated in both of them. That is not yet published, so none prevails today. Ask us if you need it sooner.
Who you contract with, how you pay, and the documents a vendor file needs. They are being revised, so dates are not final.
The legal entity is named in your order form and in the imprint. Intramedial is a Trustvice product.
TrustviceThe governing law and the courts are named in the Terms and in your order form. They are not restated here until the documents are revised.
Self-serve plans are paid by card through Avonao Billing, which handles sales tax and VAT where required. Enterprise is quoted per contract, with invoicing and purchase orders on terms agreed per contract. Ask us if you need it sooner.
Invoices are listed for the organisation in the dashboard. How tax is handled is set out in the Terms.
Providers the service uses today. The official list is not yet published, and may change before it is.
| Document | What it covers | Updated |
|---|---|---|
| Terms of Service | The agreement: accounts, fees, data, liability and governing law. | |
| Data Processing Addendum | Processor terms, security measures, breach notice, audits and transfers. | |
| Enterprise SLA | Uptime, credits and incident targets, once an Enterprise SLA is written. | |
| Sub-processors | Each provider, what it does, where, and how changes are announced. | |
All legal documents →Trust center →
Notice of sub-processor changes and of changes to the Terms and policies, by email. You confirm before anything is sent.
From the first message to the first workspace. Nothing here requires a sales call before you can evaluate: the Free plan and the demo are open to anyone.
The sales form asks for your volumes, regions, requirements and timeline. A person replies within one business day.
Your use case, the tools and volumes, the regions, and the steps your procurement needs.
Allowances, seats, retention, price and terms, ready for your review.
The order form brings any Enterprise terms into effect and prevails over the Terms where it says so.
Create a workspace in each region you need and issue scoped API keys. Single sign-on runs through Avonao ID for the plans that include it.
Runs the real admission kernel in your browser on the module pages, with no sign-up or account needed.
/modules/coordination-admit →A real account with 1 agent and 100 admissions a month, to try the plane.
/auth/signup →Check a signed ledger bundle against the published key, without an account.
/verify →Short answers, each with the document that settles it.
No dedicated key today. Bundles use Intramedial’s keys, one per jurisdiction. /docs/ledger-bundles-snapshot →
Not stated yet. Plan on the region you choose at creation staying fixed, and ask us before you rely on a move to another region later. Ask us if you need it sooner. /docs/data-regions#how-to-pick-a-region →
A DPA for Intramedial is not published yet. Ask us; it is part of the vendor file for an order form, and we will say what applies. /legal/data-processing-addendum →
Every bundle you saved stays verifiable offline against the published key, with no call to us; keep a copy of the key with your bundles. Terms for deleting an account, and for a grace period, are not yet published. We will say so when it is published. /verify →
No. Team and Scale plans include single sign-on, which is set up through Avonao ID. SCIM directory sync is planned and is not available yet. Neither is an Enterprise-only feature today. The documents are being revised for Intramedial. /docs/sign-in#single-sign-on →
Not stated yet. Self-serve plans are paid by card through Avonao Billing, and Avonao Billing issues the invoice. Invoicing and purchase orders for Enterprise are agreed per contract with us. The documents are being revised for Intramedial. /docs/billing →
| Provider compliance reports are not yet collected for sharing with customers. |
| Vulnerability disclosure | Ask us | Report it through the security form. No published disclosure policy yet. |
| Privacy Policy |
| What personal data is processed, why, for how long, and your rights. |
| Acceptable Use Policy | What may not be done with the service and how it is enforced. |
| Responsible disclosure | How to report a vulnerability, scope, safe harbour and targets. |
| Imprint | The publisher, its registration and its EU representative. |