← All projects

Interactive demo · Web App

Devotion app icon

Devotion

The whole team, inside one machine of yours

Devotion is a workspace for development teams that you host yourself. Projects, tasks, a calendar, collaborative documentation, saved commands and encrypted credentials, all synced in real time. It runs on a server of your own, and nothing in it ever leaves that server.

Nothing below is a mockup. Every screen is the running application, photographed against a workspace seeded for the occasion, and the interface is in the language you are reading.

View project

01

Everything you are building, in one place

A space holds the projects of a team, each with its colour, its state and how much of it is done. It can be yours alone or shared with whoever you invite.

02

The board, and the same work as a list

Statuses are shared across the whole space, so a task means the same thing in every project. The board is for moving things along, the list for finding them: labels, assignee, dates and subtasks in one table you can sort.

03

Meetings and the time you set aside

Every meeting in the space next to the work sessions you book for your own tasks, each in the colour of its project. Drag one to move it, and it moves for everyone.

04

Documentation that links to itself

Markdown with a contents block that builds itself, tables, code and wiki links between documents. Whoever else has it open sees your cursor, and it exports to Word or PDF with the contents intact.

05

The commands you never remember

The snippets a project actually needs, grouped and highlighted by language, one click from the clipboard. The ones the whole space shares live in the space, not scattered across five READMEs.

06

Credentials, encrypted

Passwords stay covered until you ask to see one, and the list never carries them. The space gathers its own and those of its projects, and each login says who added it.

07

What was added, and when

Every project keeps a map of what has been built into it, grouped by area. Each feature carries its improvements and fixes, and the milestones sit on the timeline along the bottom. What a connected tool proposes waits at the top until someone accepts it, edits it or throws it out.

Personal, space, project

Everything in Devotion lives at one of three levels, and the level decides who sees it. What is yours alone hangs off nobody. A space is a team, or just you, and it holds the projects. A project always lives inside a space. The same sections exist at more than one level on purpose: a password can belong to you, to the whole team, or to one project, and where you put it is the answer to who should have it.

  1. Personal only you Your own notes, commands and passwords. They hang off no space, and nobody else can reach them.
  2. Space you, or your team The projects, and whatever belongs to all of them: shared statuses, meetings, general documentation, the logins the whole team uses.
  3. Project inside a space Tasks, board, documentation, commands, meetings, its GitHub repository and its own evolution map.
The same three levels on one screen: every login you can reach, your own first, then the space, then each of its projects.

Everything, one ⌘P away

One shortcut searches every space you belong to at once, and it does not care what kind of thing it finds: projects, notes, documents, tasks, meetings, commands and passwords come back together, each under its own heading. A password comes back with a copy button beside it, so getting one into the clipboard never means opening the vault, finding the entry and revealing the field. Type, Enter, paste.

One word, and passwords, tasks, commands and documents come back together. The password copies from here without ever being shown.

What an agent can do in here

Devotion has a second door, separate from the web session on purpose: personal tokens that authenticate external tools. Behind it there are skills you download from the app itself, one for each part of the workspace, files that tell the agent what it can touch and the syntax Devotion writes in. Install them once, and from then on you ask in plain language. These are three of them.

A token is created once and shown once. After that only its first characters remain.
The skills, downloadable from the app. They are the same files this server has deployed, so there is no stale copy to keep in sync.
The setup, spelled out for Claude Code and for Codex. Four steps, and the commands are there to copy.

Deployed for

Where it is already running, day to day.