Skip to content
Epher Compute Chain epher.cc · by GINF Systems

Editions

One product.
Four deployment shapes.

Epher Compute Chain ships in four editions. The wire format, the Borz contract dialect, the proof structure, and the verifier are identical at every shape. What changes is who owns the hardware, where it sits, and how it is billed.

Public mesh

Epher Cloud

Hosted, multi-tenant, per-call EUR.

Run on GINF's EU-attested public mesh across nine EU regions. No infrastructure to operate; smallest time-to-first-entry. Bring an API key, append your first signed entry within minutes.

Billing

Per-call in EUR. See /tiers for the per-tier price table.

For

  • · EU SaaS and startups
  • · AI agent platforms
  • · Notarisation use-cases
  • · Pilots and POCs going to production

Operational properties

  • ●Operated end-to-end by GINF Systems Kft.
  • ●HATP root in EU-located HSMs
  • ●Standard DPA on file; EU sub-processors only
  • ●Both pillars enabled by default (storage + compute)
Start free →

Customer hardware

Epher Enterprise

Dedicated mesh on your DE:SH hosts. Per-host licence.

Popular

Same software, deployed on a dedicated mesh of customer-controlled DE:SH appliances. Full data residency on your premises; per-host licensing in EUR; managed updates from us via a controlled channel.

Billing

Per-host annual licence. Volume tiers available.

For

  • · Regulated mid-market (banks, insurers)
  • · Health, life sciences, public payments
  • · Companies with strict residency policies
  • · Multi-tenant ISVs requiring isolation

Operational properties

  • ●Customer-owned DE:SH appliances (Decent Edge)
  • ●HATP tenant key custody options
  • ●Private replica set; no cross-tenant blast radius
  • ●Optional Epher Cloud burst for non-resident workloads
Talk to sales →

Air-gapped

Epher Sovereign

Air-gapped, customer-controlled root, bespoke contract.

For environments where the operator cannot reach the mesh at all. Customer-held HATP root; one-way audit replication out; full lifecycle handled by customer staff with our deployment guides. Bespoke contractual terms.

Billing

Bespoke contract; site-licensed.

For

  • · Defence and intelligence
  • · Government / public-sector
  • · Critical national infrastructure
  • · Operators of classified systems

Operational properties

  • ●Customer-held HATP root key (no GINF custody)
  • ●One-way replication out; no inbound network
  • ●On-prem operations and incident response
  • ●EU and non-EU jurisdictions supported
Request brief →

Single host

Epher Community

Single-host, non-production. Free with KYC.

A community edition for evaluation, research, and education. Runs on a single host you control; no SLA; identical wire format so anything you build here ports cleanly to Cloud or Enterprise. KYC to receive a build.

Billing

Free. KYC + non-production licence.

For

  • · Independent developers and researchers
  • · University teaching and student projects
  • · Procurement evaluations
  • · Open-source ecosystem partners

Operational properties

  • ●Single-host topology, local verifier
  • ●Identical wire format; ports to other editions
  • ●No SLA; community channels only
  • ●KYC required to receive a build
Request a build →

Side by side

Which edition does what.

Property Epher Cloud Epher Enterprise Epher Sovereign Epher Community
Hardware owner GINFCustomerCustomerCustomer
Operator GINFGINF (managed)CustomerCustomer
HATP root custody GINFGINF / customerCustomer onlyCustomer (self-issued)
Inbound network needed YesOptionalNo (air-gapped)Local only
Storage pillar ✓✓✓✓
Compute pillar (contracts) ✓✓✓✓ (non-prod)
Tiers available T0–T4T0–T4T0–T4T0–T2
SLA Per published termsBespokeBespokeNone
Billing model Per-call (EUR)Per-host (EUR)Bespoke contractFree with KYC
Cross-edition replication —To Cloud (optional)One-way out only—
Suitable for production ✓✓✓Evaluation only

All editions implement the open Ephernity protocol — ephernity.org. A verifier built against the spec will accept output from any edition; the wire is the contract.

Picking an edition

Three questions that decide it.

Most customers reach the right edition by answering three questions in order. If you are unsure, talk to us — there is no penalty for starting on Cloud and graduating to Enterprise when the data needs a postcode.

  1. ⌗ 01

    Does the data have a hardware postcode?

    If your residency requirement is satisfied by an EU operator on EU hardware, Cloud is the smallest fit. If it has to live in your rack, Enterprise. If the network can't even reach it, Sovereign.

  2. ⌗ 02

    Who needs to verify it?

    If outside parties (regulators, auditors, customers) verify with the open Ephernity verifier and a published root key — any edition works. Sovereign is the right fit when the operator's own actions must also be verified by a third party.

  3. ⌗ 03

    Is this production or evaluation?

    For pilots, prototypes, teaching, or "kick the tyres" use Community — same wire, free, KYC. Promote to Cloud or Enterprise for production; everything you wrote ports unchanged.