T0
Ephemeral
Live ticks. Agent scratch state. Match sessions.
- Horizon
- 1 s
- Retention
- 1s default · configurable
- Anchor
- none (destroyed)
- Signature
- Ed25519
Talk to us
Talk to us →Tiers · Epher Cloud
Eight horizons.
One primitive.
The tier is a triple of (retention, anchoring, signature). The wire is the same; only the policy changes. T0–T4 use Ed25519 for speed; T5–T7 cross into Falcon-1024 post-quantum territory for multi-month and longer retention. Promote a ledger between tiers with a single API call — or supply any duration directly as a TTL string.
Pricing — in revision
Per-unit prices are being re-cut against the 2026-05-31 benchmark and cost data and are not published while the revision is in flight. The tier structure below — horizon, retention, anchor, signature — is stable. Talk to us for early-access quotes for Epher Cloud, per-host indicative figures for Epher Enterprise, and bespoke terms for Epher Sovereign. Epher Community is free with KYC and remains so.
T1
Session
Real-time rooms. Checkout flows. Per-tenant working state.
- Horizon
- 60 s
- Retention
- 60s default · configurable
- Anchor
- end-of-life checkpoint
- Signature
- Ed25519
Talk to us
Talk to us →T2
Operational
Operational audit trails. Monitoring windows. Application events.
- Horizon
- 1 h
- Retention
- 1h default · configurable
- Anchor
- periodic Merkle (1h)
- Signature
- Ed25519
Talk to us
Start with this tier →T3
Daily
Daily rollups. Event logs. Analytics aggregates.
- Horizon
- 1 d
- Retention
- 1d default · configurable
- Anchor
- periodic Merkle
- Signature
- Ed25519
Talk to us
Talk to us →T4
Weekly
Weekly summaries. SLA reports. Feature-tracking windows.
- Horizon
- 7 d
- Retention
- 7d default · configurable
- Anchor
- periodic Merkle
- Signature
- Ed25519
Talk to us
Talk to us →T5
Monthly
Monthly compliance windows. AI Act provenance. Project records.
- Horizon
- 30 d
- Retention
- 30d default · configurable
- Anchor
- periodic + PQC
- Signature
- Falcon-1024
Talk to us
Talk to us →T6
Compliance
Regulated records. DORA. AI Act. Audit trails for the next regulator.
- Horizon
- 1 y
- Retention
- 1y default · configurable
- Anchor
- periodic + permanent
- Signature
- Falcon-1024
Talk to us
Talk to us →T7
Eternal
Provenance attestations. Notarisation. Protocol history.
- Horizon
- ∞
- Retention
- permanent
- Anchor
- permanent (24h)
- Signature
- Falcon-1024
Talk to us
Talk to us →Pinned-region or strict-EU residency, storage usage, anchor fees, and verify-side API calls are line-itemed separately when pricing is published — no opaque bundles. The structure is stable while the numbers are revised.
Custom TTL
Any duration, not just named presets.
The eight tiers above are named presets. The ttl field
accepts any duration: a preset name, a duration string, the sentinel
"forever",
or canonical seconds as an integer. The receipt always records the resolved
canonical seconds so any verifier can check retention without knowing which
form the caller used.
{ "ttl": "T5" } // 2 592 000 s — Monthly preset
{ "ttl": "90d" } // 7 776 000 s — ninety days
{ "ttl": "5m" } // 300 s — five minutes
{ "ttl": "2h30m" } // 9 000 s — compound duration
{ "ttl": "forever" } // 0 — unbounded (equivalent to T7)
{ "ttl": 7776000 } // 90 days as canonical secondsSignature scheme follows the resolved TTL: durations below 2 592 000 s (30 d) use Ed25519; at or above that boundary Falcon-1024 applies. Promotions re-sign existing entries at the new scheme when the boundary is crossed.
Side by side
How the tiers differ — in one row.
| Tier | Horizon | Retention | Anchor | Signature | Store | Pricing |
|---|---|---|---|---|---|---|
| T0 · Ephemeral | seconds | 1s | none | Ed25519 | memory | in revision |
| T1 · Session | minutes | 60s | end-of-life | Ed25519 | memory + spill | in revision |
| T2 · Operational | hours | 1h | Merkle 1h | Ed25519 | BadgerDB | in revision |
| T3 · Daily | days | 1d | Merkle periodic | Ed25519 | BadgerDB | in revision |
| T4 · Weekly | weeks | 7d | Merkle periodic | Ed25519 | BadgerDB | in revision |
| T5 · Monthly | months | 30d | periodic + PQC | Falcon-1024 | BadgerDB | in revision |
| T6 · Compliance | 1 year | 1y | periodic + permanent | Falcon-1024 | BadgerDB | in revision |
| T7 · Eternal | ∞ | permanent | permanent 24h | Falcon-1024 | Badger + offload | in revision |
Compute pricing · Epher Cloud
Contracts: per call, by unit-of-work.
Each Borz contract step records bytes-in, bytes-out, and a deterministic operation count. On Epher Cloud these are billed at a flat per-unit rate; a step that touches a T5 state-ledger also incurs that tier's storage cost for the resulting receipt entry.
| Unit | Counted as | Notes |
|---|---|---|
| Bytes in (input payload) | per GiB | Counted at the wire after canonical encoding. |
| Bytes out (response payload) | per GiB | Excludes the ledger-entry header overhead. |
| Deterministic operations | per 1M ops | Counted by the Borz runtime; replays count the same. |
| Step receipt (one ledger entry) | underlying tier rate | A T5 receipt is metered as a T5 storage entry. |
Per-unit euro rates are being re-cut as part of the 2026-05-31 pricing revision. The units above — bytes-in, bytes-out, deterministic ops, step receipt — are stable and what the runtime already records.
Epher Enterprise tracks the same units for visibility but the per-host licence is flat; you can run as many calls as the hardware supports without per-call charges. Epher Sovereign is bespoke. Epher Community imposes a daily call cap and is for non-production use only.