Lokal and Publik

Open arkaik.app, create a project, and you are already running Lokal. There is no sign-up screen in the way. Your graph lives in your browser's own storage, so it keeps working on a train with no signal, and nothing about it touches a server.

Leaving is as easy as arriving. Export writes the whole project as one JSON file: every node, edge, status and journal entry. Import it into another browser, check it into a repo, or hand it to an agent. The file is the project.

When you want an audience, Publik publishes a snapshot and gives you a link at arkaik.app/p/{id}. Anyone with the link sees a preview (title, description, size of the graph) and can import their own copy to explore and edit locally. Think of it as a gist for product graphs.

Publik is careful about what leaves. Your journal is stripped by default, on the server side, so a forgotten flag never leaks your history. Snapshots are immutable: publishing again creates a new link. You get an owner key exactly once, and it is the only way to delete the snapshot later, so keep it somewhere safe.

No account is needed for either. Publishing works from the app or from the command line with arkaik push.