Founder of OneMana · engineer · builder
I build things that help teams work together without paying a per-seat SaaS tax every month. Right now that's OneCamp: a self-hosted, open-source workspace with chat, tasks, docs, video calls, a calendar and AI. This is where I write down what I shipped and what broke.
OneCamp's docs have the blocks people who write in Notion reach for without thinking: toggles that each reader opens for themselves, simple tables, equations, callouts, a table of contents, code blocks that draw Mermaid diagrams, and pic...
OneCamp's third look: no top bar, one sidebar that holds the workspace, search and you, a single command palette that can also answer, and every screen rebuilt to one standard. Typing in a message box does a third of ...
A colour for every person, project and channel. Themes that recolour the whole frame. Illustrations where a screen is empty. Then the speed work: a sent message shows in 16 ms instead of 489, and typing in a long doc ...
Going through every OneCamp screen for the redesign meant opening a lot of tasks and running a lot of imports. Three things happened that shouldn't have: opening a task could record an edit nobody made, an import coul...
OneCamp people have three names: a display name, a full name and an @handle. Until this release the app picked between them differently on every screen, and anyone who joined before handles existed had none. Now there...
A new teammate in OneCamp now lands in #general with the message box ready, however they get in: an invitation, Google, GitHub, single sign-on or the directory. Invitations say where they stand, a whole company can jo...
An AI agent in OneCamp used to run every tool with its owner's access, for anyone who could message it. Now each run knows who asked, and reaches only what both that person and the owner can. Text from outside your wo...
The anti-SaaS workspace. Chat, kanban boards, collaborative docs, video meetings, calendar sync, and a local AI assistant, all running on your own server. No per-seat pricing.
A multiuser whiteboard and chat, with no database.
Fault tolerance in monitoring distributed systems. The leader node checks the CPU and memory use of each server and commits that data to every server.
A REST API that runs health checks and tells the user when the status of a response code changes.
I write when something ships or breaks, which is often. Follow along in your feed reader, or on X.