Plans for teams building systems that move money
Start with the open-source ledger. Move into a managed cloud pilot when your team needs hosted operations, onboarding, and production planning.
From open-source adoption to managed production
Managed Cloud is not public self-serve yet. Requests route through onboarding so the right deployment path is approved before access is issued.
Open Source Core
Install LedgerForge in your own environment and build with the full double-entry ledger API.
Managed Cloud Pilot
A guided managed environment for teams that want a hosted ledger workspace before production rollout.
Enterprise Deployment
Dedicated production deployment, migration help, and operating support for teams moving real money.
See which path fits your team
Frequently asked questions
Questions about pricing or managed access can go directly to support@ledgerforge.io.
Where is my ledger data stored?
If you self-host LedgerForge Core, your ledger data remains in your infrastructure. Managed deployments are scoped during onboarding so storage, region, backup, and access-control requirements are agreed before rollout.
What is a connected instance?
A connected instance is a self-hosted LedgerForge Core deployment linked to a managed workspace for operations, monitoring, and back-office visibility without changing ownership of the underlying ledger service.
What happens if I disconnect my instance?
Your self-hosted Core continues running independently. The managed workspace stops showing live operational data until the connection is restored.
What happens if I exceed plan limits?
Pilot usage is reviewed with your team before production traffic. Enterprise plans define throughput, storage, support expectations, and overage terms during the contract stage.
Can I migrate from another ledger system?
Yes. Most migrations start by importing balances, replaying historical transactions where needed, and running LedgerForge alongside the existing system before cutting over workflows.