The missing data tool

Manage your data, understand it, and integrate it into your workflows.

Get started Learn more

How it works

Define the schema

Model data as a graph of connected roles and typed properties.

This matches your mental model. No more squeezing data into tables or trees.

Role membership is dynamic and n-ary, making data evolution painless.

Scroll to continue

Animated app walkthrough

Coming soon...

Use cases

Saka understands the structure and relationships of your data. Use it to model, modify, validate, and analyze your data.

Translation catalogs

Model locales, keys, variants, and review status, then export validated translations for an app or game.

View template

Video game content

Keep items, characters, quests, stats, and their relationships consistent as a game world grows.

View template

Asset libraries

Catalog files, owners, licenses, tags, and usage so creative assets stay findable and safe to reuse.

View template

Research collections

Organize sources, samples, observations, classifications, and citations in a queryable model.

View template

Equipment inventories

Track equipment, locations, specifications, assignments, and maintenance without a heavyweight inventory system.

View template

Configuration data

Define typed settings, environments, feature rules, and dependencies, then export the format your software expects.

View template

The language

Define your model, manage values, and query the result with one composable relational language.

Define types

set Product = (
  name: str
  vendor: str
  stock: num
  price: num
)

Define values

var products* Product = {
  (
    name: "pen"
    vendor: "acme"
    stock: 2
    price: 3
  )
}

Update values

products |= (
  name: "book"
  vendor: "acme"
  stock: 4
  price: 10
)

Query values

def inventory_value =
  products
  if .stock > 0
  map (
    name: .name
    value: .price * .stock
  )

Define functions

def lin total_value(p: Product): num = {
  p.price * p.stock
}

Use functions

def total_inventory_value =
  products
  map total_value(.)
  agg sum(.)

Explore the language docs

Versus Spreadsheets

Spreadsheets offer unparalleled flexibility. But they don't help with data integrity or understanding. That's where Saka shines.

NeedSpreadsheetSaka

NeedStructure

Spreadsheet

Meaning depends on column names, cell values, and conventions users can bypass.

Saka

Types and entity definitions validate the shape of every value.

NeedRelationships

Spreadsheet

IDs, lookups, and duplicated fields connect sheets by hand.

Saka

Relationship properties connect entities directly, including n-ary and polymorphic relationships.

NeedQueries

Spreadsheet

Filters and formulas scatter query logic across cells and sheets.

Saka

Relational queries compose over the data model and update in real time.

NeedProgrammability

Spreadsheet

Most data work happens manually through the grid and menus.

Saka

A native REPL can inspect, query, and update data programmatically.

Versus Alternatives

Saka's unique technology unlocks superpowers you won't find in other spreadsheet–database hybrids.

Design choiceAlternativesSaka

Design choiceData model

Alternatives

Fixed tables hold records; link columns connect one table to another.

Saka

A graph connects typed entities, with membership that can change dynamically.

Design choiceProgrammability

Alternatives

Formula languages transform rows inside individual tables.

Saka

One relational language manages types, values, updates, queries, and functions.

Design choiceQueries

Alternatives

Scalar expressions operate on one table's rows.

Saka

Relational queries compose across the full data graph.

Design choiceDelivery

Alternatives

Cloud-hosted storage and server-backed calculations.

Saka

A local in-memory engine keeps editing responsive and files portable.

Frequently asked questions

A few things to know before you get started.

What is Saka best suited for?

Saka is the best tool for managing structured data with complex relationships. It's a better alternative to spreadsheets, JSON/XML/CSV files, and SQL databases for development workflows.

How scalable is Saka?

TODO

When is Saka not the right fit?

Consider alternatives if your data is unstructured or very large (more than 1 million data items).

Is Saka a database?

Saka has an in-memory database engine and an export file format, but it is not a transactional database system.

Does Saka support SQL?

No. Saka does not support SQL and cannot connect to SQL databases.

Can I import and export my data?

Yes. Saka supports importing and exporting database files, so you can keep a copy of your work and open it again later.

Do I need an account?

No account is required to try the current Saka experience. Open Saka and start a database from scratch or import a database file.

Is Saka free?

Saka's core features are free. Paid plans with additional features are planned for later, but their pricing, and availability have not been decided.

Is Saka open source?

Saka is a closed source commercial product. This allows us to continually invest in making Saka a better product for everyone.

Who is behind Saka?

Sufyan Dawoodjee in Mountain View, California, USA

Is Saka ready for production?

No. Saka is still in alpha. Saka works, but bugs and missing features mean you should not rely on it for production workflows just yet.

Data loss is a real risk.

Still have a question? Get in touch.

Ready to try Saka?

Create a database from scratch or import an existing file.

Get started Read the docs