SQLStyle

Launch special available

SQLite backups, replication, and failover—without cluster machinery.

No credit card required

01 / Continuous backups

Keep SQLite local. Put its history in your storage.

Backup and restore →

Application process

SQLite database on local disk

Full snapshots + incremental history

Your infrastructure

S3-compatible object storage

Point-in-time restore

Replay verified history through a selected commit timestamp.

02 / Direct replication

Add an instance. It gets its own live SQLite replica.

Replication architecture →

Primary instance

Local SQLite

Reads and writes

Direct stream

Replica instance

Local SQLite

Reads from local disk

Lightspeed replication latency

Same-host, commit-to-commit measurement with synchronous=OFF.

03 / Automatic failover

The primary is a role, not a special deployment.

Primary and failover →

Hosted controller

Primary authority

Assigns one instance to write and can transfer that authority to a replica.

No in-cluster election

Application instances do not choose the primary.

Stale authority rejected

A former primary cannot resume writing after authority moves.

04 / Application Stored Procedures

Give every instance the same write interface.

An Application Stored Procedure (ASP) is a typed database operation defined in application code. The SDK runs it locally on the primary or routes the call there from a replica.

Application Stored Procedures →

Abbreviated ASP definition and call

// Named-map MessagePack is implicit.
addTodo, err := sqlstyle.DefineIASP(
    config,
    "todos.add",
    func(ctx context.Context, tx *sql.Tx, payload AddTodo) (AddTodoResult, error) {
        result, err := tx.ExecContext(ctx,
            "INSERT INTO todos(title) VALUES (?)", payload.Title)
        if err != nil { return AddTodoResult{}, err }
        id, err := result.LastInsertId()
        return AddTodoResult{ID: id}, err
    },
)
if err != nil { return err }

result, err := addTodo(ctx, AddTodo{Title: "ship it"})

Pricing

Start with Launch special.

Launch special includes the SQLStyle runtime and hosted controller.SQL reads and writes against your SQLite databases are not metered; the allowances below apply only to persistent controller-state updates.

What counts as a controller-state write? →

Launch special

$0per month

  • ✓3 hosted controllers
  • ✓10,000 controller-state writes per month
  • ✓CLI account workflows
  • ✓No credit card required
Create account

FAQ

Deployment questions.

hello@sqlstyle.com →
Where does my data live?+

SQLite files remain on the application instances. Replication runs directly from primary to replicas; snapshots and incremental history go to the configured S3-compatible object storage.

Is SQLStyle a hosted database?+

No. SQL, replication, and backup operations run from the application processes. The hosted component holds coordination state and assigns primary authority.

Does SQLStyle limit database writes?+

No. Plan allowances apply to controller-state writes: persistent updates made by the hosted controller to coordination data such as authority and failover state. SQL reads and writes against your SQLite databases do not consume the allowance.

Launch special · $0/month

Run the full system before you pay for more capacity.

Launch special includes 3 hosted controllers and 10,000 controller-state writes per month. Database reads and writes are not metered.