Frequently Asked Questions

Horizon is a proof infrastructure that captures and seals business decisions as they happen, creating an immutable, cryptographically-secured timeline.

No. The append-only architecture means no mechanism exists to modify or delete sealed facts. This is an architectural constraint, not a policy.

Horizon stores your declarations (custom_payload), actor identifiers, authoritative timestamps, and hash chain links. It does not interpret or validate your data.

No. Horizon proves that someone declared something at a specific time. It's a witness to declarations, not to reality. The truth of declarations requires independent verification.

Verification requires only the bundle and Horizon's public key. Recompute hashes, verify the chain linkage, and verify the Ed25519 signature. No network access to Horizon is needed.

Exported proof bundles remain valid and verifiable forever. They are self-contained and only require the public key for verification.

Yes. Data is tenant-isolated at the architectural level, encrypted in transit and at rest, and your custom_payload is opaque to Horizon: we don't parse or analyze it.

Horizon provides the cryptographic foundation for compliance (immutable audit trail, authoritative timestamps, tamper detection). Your compliance program defines how to use it.

SaaS (Horizon-managed), On-Premise (your infrastructure), and Air-Gapped (no external connectivity). All options provide identical cryptographic guarantees.

Start with the First Seal guide to seal your first fact in 5 minutes. Then see the API Reference for complete endpoint documentation.