KIZAKI

For twenty-five years, computing was something institutions ran and everyone else received. Banks were clearing your checks by 1959. Airlines were booking your seats by the early sixties. Companies too small for a mainframe rented computer time by the hour. Then came 1979 — VisiCalc, the first spreadsheet, and people started buying $2,000 Apple IIs just to run a program. The personal computer brought something different: computation you operated yourself.

Look at how the software you rely on actually runs today. An organization is hundreds of little tools stitched together — data flowing between services nobody has mapped, one team's change quietly breaking another team's dashboard, every new internal app another round of wiring, deployment, and security review. AI has made writing code nearly free, but it left everything around the code exactly as painful as before. The bottleneck was never typing the software. It was running it.

Kizaki is a workspace where software is a medium, built on one backbone: microapps — small, fully custom full-stack applications — composed through a typed dependency graph, with computation in isolated sandboxes and your existing systems wired in once. It has two surfaces. Kizaki Platform is where persistent software lives: internal tools, workflows, and portals that inherit your organization's auth, security, and audit trail the moment they're created — on a visual canvas where the dependency graph is explicit, so the platform warns you what a change will break before it breaks it. Kizaki Notebook is that same backbone inside your documents: pull live data into a page, chart it, sketch a prototype, write your reasoning around it, and share the whole thing — computation as close at hand as a paragraph.

There's a deeper layer too. Some work depends on personal judgment, and personal judgment cannot be outsourced — what you'd flag, what you'd wave through, why this one and not the nearly identical other one. That knowledge exists only in you, and it's the difference between an answer and your answer. In Kizaki, you start from a working workflow and simply use it: agree, disagree, say why. Your corrections accumulate into a working model of how you decide — visible, testable against your own history, and yours to keep, even as the workflow underneath keeps improving. We call this personally authored computing, or PAC.

All of it rests on ownership. Kizaki is local-first: your data lives on your devices and syncs in realtime, every change is attributable and revertible, and code stays the source of truth. The data engine underneath, Seaglass, is open source. The personal computer gave people computation they operated themselves; we're building the same thing for the software era — software you own and operate, instead of software that happens to you.

If that's a future you want, we'd love to have you request early access.

Cheers!

Joshua, Andy, and Bernice

The Kizaki Team