baseledger.io

What is it

Base Ledger positions itself as an "open-source wallet primitive for AI and prepaid SaaS." It is not a traditional end-of-month billing engine; instead, it performs real-time balance authorization before API calls: Reserve first, Spend upon success, and issue a millisecond-level hard decline if the balance is insufficient. This prevents budget overruns, duplicate charges, and race conditions in AI Agent or high-concurrency SaaS scenarios.

Core Capabilities

The page claims an internal latency of less than 5ms, throughput of up to 10k TPS, and a default 99.9% uptime. Architecturally, it is based on Apache Pekko and Event Sourcing, with wallet states residing in the memory of a single Actor to avoid database row locks; each transaction is written to an immutable log, facilitating financial and compliance audits. Features include Add, Reserve, Spend, idempotency keys, TTL holds, metadata, RBAC, encryption, Webhooks, event streams, and real-time analytics.

Developer Experience & Deployment

Public examples primarily feature a TypeScript/JavaScript-style SDK, and also demonstrate the REST interface POST /wallet/{id}/reserve. The open-source version supports PostgreSQL and Docker Compose, suitable for local or self-hosted deployment; the cloud version can be upgraded to managed DynamoDB infrastructure, while the enterprise version supports deployment to your own AWS/GCP VPC (BYOC). However, the text does not disclose the license, GitHub URL, additional language SDKs, or detailed deployment documentation.

Pricing & Ecosystem

Pricing is relatively clear: Open Source is free; Cloud Starter is $49/month, including 100k transactions and 1 ledger; Pro is $199/month, including 1M transactions and unlimited ledgers; Enterprise is custom, including dedicated instances, BYOC, SLA, and account managers. It emphasizes that it does not replace Stripe or Metronome, but rather handles prepaid real-time authorization first, then hands off trusted events to the billing system.

Pros, Cons & Who It's For

Pros include precise positioning, a simple API model, a great fit for AI token usage control, and a migration path from self-hosted to cloud-hosted. Cons are that the product is still in Early Access / v0.0.1 stable, with insufficient public information on ecosystem, SLA, overage billing, and SDK coverage. It is suitable for engineering teams building systems for AI Agents, pay-as-you-go APIs, in-game currencies, credits, marketplace fund holds, etc.

Access from China

The main text provides no information on Chinese nodes, ICP filing, payment methods, or access availability, so the status of access from China can only be deemed unknown. Domestic teams looking to use it in production should focus on verifying network latency, data compliance, cloud regions, USD payments, and whether it can be fully self-hosted. Alternatives to compare include Stripe Billing, Metronome, Lago, Kill Bill, and OpenMeter.