The whole operation, offline

Family-run caterers run on spreadsheets, message threads and memory. Folio puts bookings, menus, kitchen prep, customer records, billing and backups into one workspace, and keeps working when the connection does not.

Kind: Product · side project
Status: In development
Platforms: Desktop (Windows, Linux, macOS) · Android · Web
Stack: Next.js · Tauri 2 · Flutter · Node.js · Rust
Data: SQLite on device · PostgreSQL / Supabase when hosted
Source: github.com/IncuForge/folio →

01 · Operations

The day, on one screen

An upcoming-bookings dashboard, event scheduling that carries multiple sessions and guest counts, a monthly calendar and status tracking, with customer records attached to the events they belong to rather than filed somewhere separate.

Folio daily bookings and kitchen operations board

02 · Money

Payments that arrive in stages

Catering is rarely paid in one go, so the schedule handles one, two or three stages with settlement logic behind it. Revenue and collections reporting sits on top, and overdue balances surface without anyone running a query.

03 · The library

Written once, reused every event

A dish database carrying availability and pricing, package kits assembled from it, and generated output that leaves the building: branded receipts, menu PDFs and kitchen preparation sheets.

Folio reusable menu library and local backup archive

04 · Local-first

Your data, on your device

Desktop keeps a local SQLite database with portable, validated backups and automatic retention, taking a safety copy before any restore. Android runs standalone or pairs with the desktop over LAN, VPN or Tailscale, with manual sync and explicit conflict recovery rather than a silent merge.

3

Platforms from one project · desktop, Android, web

4

Desktop targets built in CI

0

Cloud services required to run it

Counted from the source

Nothing estimated

Atlas

→