Why Saka
Saka helps you manage small data: reading lists, inventories, schedules, prices, and other collections of fewer than 100,000 records.
Why Saka
Section titled “Why Saka”Spreadsheets are easy to start with, but relationships between data can be hard to manage. Databases let you describe those relationships and ask questions, but editing their data can be tedious. Files such as JSON and YAML become harder to manage as they grow.
Saka lets you structure and query data like a database, see it in a live grid, and keep it in a file.
Use cases
Section titled “Use cases”Personal: reading lists, household inventories, trip expenses, service records, and tasks.
Business: price sheets, staff schedules, equipment registers, project trackers, and deployment settings.
When not to use Saka
Section titled “When not to use Saka”- Documents and media: Saka is for structured data.
- Millions of rows: Saka targets data you can edit interactively.
- Managing a SQL database: Saka uses its own language and storage. It does not connect to Postgres, MySQL, or SQLite.
- Running a live application’s transactions: Saka is not built to serve concurrent writes.
Alpha status
Section titled “Alpha status”Saka is in alpha and is not ready for production use. Features may change and data may be lost. Keep independent backups.
See the roadmap for priorities and the changelog for releases.
Where to next
Section titled “Where to next”- Language tutorial: learn SakaQL.
- Application guide: use the app.