Skip to content
LedgerForge Cloud

The LedgerForge ledger, operated for you

Today, our team runs a dedicated LedgerForge deployment for each customer, with upgrades, backups, monitoring, scheduled verification and support included. A hosted multi-tenant service with its own dashboard comes next.

Request accessBook a demo
What we operateAvailable today
  • API servers and workersProvisioned, scaled and upgraded
  • PostgreSQL and RedisBackups and monitoring
  • ledgerforge verifyRun on a schedule
  • Audit checkpointsExported and anchored
  • Agent keys and policiesDesigned with you

You keep the API, the data model and the open-source core. We keep it running.

Who it's for

For teams that need the ledger to be right, not another system to run

  • Fintech product teams

    You're building wallets, payouts, marketplace settlement or metered billing, and you want an exact, verifiable ledger without staffing PostgreSQL operations, worker fleets and upgrade windows.

  • Teams putting agents near money

    You're letting AI agents or automated workflows initiate transfers. You want spending policies, delegated budgets and independent approvers designed correctly from the first key.

  • Platforms that answer to auditors

    Partners, banks or auditors ask how you know the ledger is intact. You want regular replay checks and anchored checkpoints you can hand over as evidence.

Available today

What a managed deployment includes

Each customer gets a dedicated LedgerForge deployment operated by our team. Scope, environments and response times are agreed in writing.

  • Dedicated deployment per customer

    We provision and operate a LedgerForge deployment for your team on dedicated infrastructure.

  • Upgrades and migrations

    Release upgrades planned with you, migrations run in agreed windows and verified afterwards.

  • Backups and monitoring

    PostgreSQL backups, and monitoring of the API, workers and queues.

  • Scheduled verification

    Scheduled ledgerforge verify runs with audit checkpoints exported and anchored for each deployment.

  • Policy and approval setup

    Help designing spending policies, delegated keys and independent approvers for agent keys.

  • Onboarding and support

    Integration onboarding, then support with response times agreed for your deployment.

Planned

Coming next: multi-tenant Cloud

See the roadmap
  • Hosted multi-tenant service. Sign up and get a ledger without a dedicated deployment.
  • Dashboard. Ledgers, balances, transactions, policies, approvals and audit checkpoints in one place.
Design preview: planned

A first look at the planned Cloud dashboard

Ledgers, balances, transactions, policies, approvals and audit checkpoints in one place. This is a design concept for the multi-tenant service on our roadmap, not a product you can use today.
Design preview: plannedConcept for the multi-tenant Cloud dashboard. Not available yet.
Design preview of the planned multi-tenant LedgerForge Cloud dashboard, drawn in code. It is not a live product or a screenshot; values reuse the API samples shown elsewhere on this site.
How access works

From request to production in four steps

  1. 01

    Request access

    Tell us about your use case, expected volume and timeline using the form below.

  2. 02

    Scoping call

    We review your account model, integration, data location and support needs, then send a written proposal.

  3. 03

    Dedicated deployment

    We provision your LedgerForge deployment on dedicated infrastructure, with keys, policies and verification configured.

  4. 04

    Onboarding

    We work with your engineers through integration and go-live, then support you at the response times we agreed.

FAQ

Cloud questions

Where is my data stored?

On infrastructure dedicated to your deployment. The hosting location is agreed with you during scoping, before anything is provisioned, and recorded in your agreement.

Am I locked in?

No. Cloud runs the same Apache 2.0 core that is on GitHub, with the same API, data model and verification commands. If you leave, you can run it yourself with your data and your exported audit checkpoints.

Can I move an existing self-hosted deployment to Cloud?

Yes. We plan the migration with you: a verified backup of your PostgreSQL database, an upgrade to the current release if needed, replay and chain verification before and after the move, and a cut-over window you approve.

Is the dashboard available?

Not yet. The dashboard shown on this page is a design preview of the planned multi-tenant service. Managed deployments today are operated through the same HTTP API, CLI and MCP server as the open-source core.

How is Cloud priced?

Per deployment, based on the scope we agree on the scoping call: environments, expected volume, verification schedule and support level. You receive a written proposal before any commitment.

What do we still own?

Your application, your account model and your connections to banks or payment providers. LedgerForge records money movement and enforces key policies; it doesn't move funds on payment rails.
Request access

Request LedgerForge Cloud access

Tell us what you're building. We reply to every request, usually with a few questions and a time for a scoping call.
  • A scoping call with the team
  • A written proposal before any commitment
  • No change to the open-source core you'd run

Prefer email? Write to support@ledgerforge.io.

Please don't include API keys, secrets or customer data.

We use these details only to reply to you. See the privacy policy.