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

Network

A network,
not a vendor.

The substrate underneath Epher Compute Chain is a federated mesh of EU-domiciled operator nodes that speak an open protocol. Today GINF Systems Kft. runs the reference public mesh; customers on the Enterprise and Sovereign editions run their own meshes on their own hardware. Independent third-party operators are expected — and welcomed.

Mesh shapes

One protocol. Three operational shapes.

Public mesh

Epher Cloud

A multi-tenant mesh operated by GINF Systems across nine EU regions. The reference deployment of the protocol; smallest time-to-first-entry.

Dedicated mesh

Epher Enterprise

A single-tenant mesh on customer-controlled DE:SH hosts. Same software, private blast radius, full data residency under the customer's roof.

Sovereign mesh

Epher Sovereign

Air-gapped mesh with customer-held HATP root and one-way audit replication. For environments where the operator cannot reach the wire at all.

All three shapes verify against the same root format. A verifier built for the public mesh accepts entries and contract receipts from a sovereign mesh (when its root key is published) and vice versa — the wire is the contract.

Epher Cloud regions

Operator footprint

Reference EU presence

Primary Replica Edge
eu-fra eu-par eu-ams eu-war eu-mil eu-mun eu-lon eu-bru eu-bud eu-buc eu-mad eu-cph eu-sto

Primary points of presence host writes and signing under HATP attestation; replicas keep Raft-consistent copies; edge nodes terminate reads. All facilities sit within EU member states under EU operator control.

Topology

Three roles, each accountable.

primary

Signing host

Holds an HATP host key inside a measured-boot KVM enclave. Accepts writes, signs entries, commits via Raft. One per region, geographically pinned.

replica

Raft follower

Maintains a consistent copy of every ledger in its consensus group. Serves reads; verifies signatures on ingest; failover targets.

edge

Verifying edge

Caches recent ranges and inclusion proofs. Read-only and stateless; can be operated by third parties without holding tenant trust.

Participation

The network is meant to grow open.

The protocol is published; the wire format is canonical; the verifier runs offline. By design, the operator is not the trust anchor — the root key is. That means more than one operator can run a node, in more than one jurisdiction, without forking the system.

We expect an EU-wide federation of node operators over time — additional sovereign jurisdictions, additional anchor backends, additional verifying edges. Whether and how participation is incentivised at the network layer is a question we keep deliberately open and will work through publicly with the operator community before any change is made.

Federation

What stays true, no matter who runs the node.