Simple, usage-based pricing.
You pay for what you actually run inside the enclave — measured by the enclave itself, priced in credits. One membership covers a generous monthly allowance, and you only top up if you go beyond it. No surprise bills, no per-seat lock-in.
How credits work
One credit is £0.000001. Every metered operation has a fixed credit price, so the same workload always costs the same.
Usage is counted inside the hardware-protected enclave — the only place that knows what really ran — and reported over an attested channel. You are billed for real work, not estimates.
Credits are drawn from your balance as you go. Top up any amount in advance; when the balance reaches zero an app pauses, while staying fully attestable.
Membership
Developer membership
Includes 10,000,000 credits every month (a £10/month allowance) — enough for around 200,000 signatures, 27 hours of full-core compute, or any mix of the operations below. Overage is drawn from your pre-paid balance.
Manage billingReserved WASM capacity
Reserve 400 MB of dedicated enclave (EPC) memory for your WASM modules with unlimited, unmetered usage. Ideal for heavy, steady workloads that would otherwise run past the credit model. (Dedicated machines for container apps are priced below.)
Contact usWASM modules — price book
Lightweight WebAssembly modules running in Enclave OS Mini. Per-KB charges round up to the next KB (1 KB = 1024 bytes).
| Operation | Price | Basis |
|---|---|---|
| WASM compute (gas / fuel) | 10 credits / 1,000,000,000 instructions | ≈ 100 credits per CPU-second (≈ £0.0001/s). |
| App deployment | 100,000 credits + 500 / KB | Includes the reproducible build. Per compiled artifact size. |
| Ledger read | 100 credits + 10 / KB | Per sealed key-value read. |
| Ledger write | 200 credits + 100 / KB | Per sealed key-value write. |
| Crypto — digest | 1 credit / KB | SHA-256 / 384 / 512 over the input bytes. |
| Crypto — encrypt / decrypt | 10 credits / KB | AES-GCM over the plaintext / ciphertext bytes. |
| Crypto — sign | 50 credits / call | ECDSA signature with an enclave-held key. |
| Crypto — verify | 5 credits / call | Signature verification. |
| Crypto — random | 1 credit / byte | Hardware RNG (RDRAND) inside the enclave. |
| HTTPS fetch | 1,000 credits + 10 / KB | Standard outbound HTTPS. Per request + response body. |
| HTTPS fetch (RA-TLS policy) | 50,000 credits + 10 / KB | Attested, enclave-to-enclave verified fetch. |
| Auth & keystore SDK | Free | Not metered in v1. |
Container apps — two ways to host
Full applications running inside a confidential VM (Enclave OS Virtual). You choose the hosting model when you deploy: a size on a shared confidential host, or a whole dedicated machine of your own. Both bill per started hour from the same credit balance, and both give your app its own encrypted volume and attested identity.
Shared confidential hosts
pay per sizeThe default. Your app runs at a fixed Confidential-* size on a shared confidential VM, isolated in its own encrypted container volume with enforced CPU and memory limits. You pay only for your size, only while deployed; when a location fills up the platform provisions new shared capacity automatically.
| Size | vCPU | RAM | Storage | Credits / hour | ≈ £ / month |
|---|---|---|---|---|---|
| Confidential-Micro | 1 | 4 GB | 80 GB | 60,000 | £43.20 |
| Confidential-Small | 2 | 8 GB | 160 GB | 120,000 | £86.40 |
| Confidential-Medium | 4 | 16 GB | 320 GB | 240,000 | £172.80 |
| Confidential-Large | 8 | 32 GB | 640 GB | 480,000 | £345.60 |
| Confidential-XLarge | 16 | 64 GB | 1280 GB | 960,000 | £691.20 |
Charged per started hour while deployed. The size is chosen at deploy time and a redeploy with a new size is the resize. At zero balance the app is paused with reason “credits exhausted”, staying fully attestable.
Dedicated confidential machines
pay per machineA whole confidential VM provisioned on demand in minutes, owned by your account and operated by us. You pay for the machine, not per app: run as many of your own apps on it as you like, with resource caps entirely your call. Stop it when idle and pay only for retained storage; start it again and your encrypted volumes are exactly where you left them.
| Machine | Shape | vCPU | RAM | GPU | Credits / hour | ≈ £ / month |
|---|---|---|---|---|---|---|
| Confidential-Medium | c3-standard-4 | 4 | 16 GB | – | 240,000 | £172.80 |
| Confidential-Large | c3-standard-8 | 8 | 32 GB | – | 480,000 | £345.60 |
| Confidential-GPU-H100 | a3-highgpu-1g | 26 | 234 GB | 1× NVIDIA H100 80GB | 7,000,000 | £5,040 |
Charged per started machine-hour while the VM runs; the apps on it accrue no per-app compute charges. A stopped machine keeps its encrypted volumes and vault keys for 200,000 credits (£0.20) per GB per month after a free grace window. The GPU machine serves confidential AI: you pay for the machine, and your users pay per inference token. Paris (France) at launch; the H100 runs in the Netherlands.
On your own hardware
Confidential AI software licence
Run the Privasys Confidential AI stack on your own H100 hardware, on premises or in your cloud: attested inference serving, sealed transport and per-token billing, with updates and support from us. Unlimited use.
Contact usAttribute marketplace
Any confidential app can provide attested attributes — a verified insight such as “over 18” or “genuine document” — and any relying party can consume them, paying per disclosure. The provider earns 85% of each fee, the platform takes 15%, and the user's identity is never revealed to the platform. Prices below are Privasys's own gov-verified identity attributes; third-party providers set their own in their attested manifest.
| Attribute | Assurance | Price / disclosure |
|---|---|---|
| Age over a threshold (18, 21, …) | Gov-verified | 10,000 credits ≈ £0.01 |
| Nationality | Gov-verified | 10,000 credits ≈ £0.01 |
| Given / family name | Gov-verified | 10,000 credits ≈ £0.01 |
| Document valid (a genuine ID was verified) | Gov-verified | 10,000 credits ≈ £0.01 |
Consuming an attribute is additive to the compute your own app uses; the fee is charged to the relying party at the point of disclosure. A user proving their own attributes to themselves pays nothing.
What that looks like in practice
A typical function call
A 10,000,000-instruction call costs 1 credit — about £0.000001.
One CPU-second of compute
100 credits ≈ £0.0001.
Deploy a 1 MiB module
100,000 + 1024 × 500 = 612,000 credits ≈ £0.61, build included.
Write 8 KB to the ledger
200 + 8 × 100 = 1,000 credits.
200,000 signatures
10,000,000 credits = £10 — exactly one month of the included allowance.
An attested RA-TLS fetch (4 KB up, 64 KB down)
50,000 + 68 × 10 = 50,680 credits ≈ £0.05.
Questions about pricing?
Talk to us about volume discounts, dedicated machines, larger GPU fleets, or anything else. We are happy to help you model your costs before you commit.