Service Level Statement

Last updated: June 5, 2026

Ledgerwire is a paid early-access service operated by Ledgerwire LLC. We provide the service on a best-effort basis. This page describes what that means concretely and what you can expect from us.

Availability target

We target greater than 99% monthly availability of the core Ledgerwire HTTP service (https://ledgerwire.io and the MCP endpoint at /mcp).

This target is best-effort. We do not currently offer service credits or contractual remedies for failing to meet it. As Ledgerwire matures and we move past early-access, we expect to formalize a measured SLA with credits. Until then, we make the following operational commitments:

• We monitor availability continuously and are paged on outages.
• We will work to restore service as quickly as practicable.
• We will communicate the status of major incidents through email to active subscribers, and post-incident retros for any outage longer than 30 minutes.
• We will not knowingly take the service offline without advance notice except in response to an active security or stability incident.

What’s covered

The availability target covers the Ledgerwire HTTP service responding to authenticated requests with HTTP 200 within 10 seconds, including:

• Dashboard sign-in and account management
• MCP token creation, listing, and revocation
• The MCP endpoint serving authenticated tool calls
• Webhook delivery from billing and aggregator partners

What’s not covered

The availability target does not apply to:

• Upstream open-banking aggregator outages. When Quiltt, Finicity, or your financial institution is unreachable, Ledgerwire may return partial or stale data. We treat these as service-degraded events and surface them to you in API responses, but they are not counted against the availability target.
• Email delivery delays. Magic-link sign-in emails are delivered by a transactional email provider on a best-effort basis. Delays of up to 10 minutes are normal and not considered an outage.
• Scheduled maintenance. We perform brief deployments and database maintenance during low-traffic hours. These typically take less than 60 seconds and are not counted against the availability target.
• Force majeure events. Outages caused by hosting provider failure, upstream network outage, natural disaster, or other events outside our reasonable control.

Backups and recovery

The application database is continuously replicated to encrypted off-site backup storage. Backups are retained for 24 hours; no point-in-time recovery is available beyond that window. In a worst-case data-loss event, up to 24 hours of recent account changes — such as a newly connected bank or a recently issued access token — may need to be re-done. No financial transaction history is lost, because Ledgerwire does not store it: transaction and account data are re-fetched live from your institutions on each request.

Status communication

For ongoing incidents and post-incident retros, write to support@ledgerwire.io. A public status page is planned for a future release.

Changes to this document

We may update this statement as Ledgerwire matures. Material changes will be communicated via email to active subscribers in advance of the change.