Skip to main content

Kurabase reference

Kurabase is an experimental relational data layer whose canonical state is committed to an EVM-compatible chain. It gives application developers database-shaped primitives: tables, SQL migrations, filters, policies, projections, and a small JavaScript SDK.

The target is a developer experience inspired by Supabase, not a compatibility wrapper around Supabase or PostgreSQL.

What is implemented​

  • Versioned, atomic SQL migrations.
  • CRUD, common PostgREST-style filters, projections, relation selection, and returning semantics.
  • Row-level security evaluated by a delegated gateway.
  • SQL-language RPC for scalar, table-returning, and atomic mutating functions.
  • An independent fetch-native @kurabase/js client.
  • Local Anvil, gateway, administrative gateway, and Dashboard startup through kura start.

What is canonical​

The chain records canonical instance state. A gateway can hold a local relational projection to make joins, aggregates, CTEs, views, and window functions practical. That projection is rebuildable and is not an independent source of truth.

Read this before building​

Kurabase is a hackathon implementation for local development and exploration. It does not claim public-chain confidentiality, production availability, complete PostgreSQL compatibility, PostgreSQL wire compatibility, a general-purpose smart-contract security review, storage, realtime, or a hosted authentication provider.

Unsupported SQL must return an explicit error. It must not silently approximate a result.

Next: run the local stack.