Portfolio, not a to-do list
Progress by weighted milestones, and "built" kept strictly separate from "live".
The operating system for digital projects
Every project, domain, renewal, invoice and server you look after — in one place that tells you what needs attention today.
Questions a task list cannot answer
- How many projects are finished but still not live?
- Which domain expires next, and who pays for it?
- How much do we spend on SaaS every month?
- Which project is at risk, and why exactly?
- Which sites are down right now?
- Which client still owes us money?
- Where is this project's repository, server and database?
- Did that project actually make any money?
These are operations questions, not to-do questions. That is the gap this fills.
What it does
Digital assets belong to projects
Domains, hosting, repositories, mailboxes, servers and subscriptions, each attached to the project and client it serves.
One renewal list
Seven kinds of expiry date in one view, sorted by date, with the cost per currency. Nothing lapses because it was on a different page.
Risk you can argue with
A rule engine, not a score: every "at risk" comes with the overdue tasks, late milestones and open blockers behind it.
Per-project profit
Contract value minus expenses, infrastructure and logged time. Integer amounts, per currency, never mixed.
Roles that hold at the server
Nine roles with real permissions, plus a client portal that shows progress and hides everything internal.
Who it is for
Independent developers, one-person studios, web and app agencies, small IT companies and maintenance shops — anyone who delivers digital work and then has to keep it alive.
Where it draws the line
- Workspaces are isolated in the database, not in the interface. Every protected query carries its workspace condition.
- It is not a password vault. It stores where to find a credential, never the credential.
- Permission checks run on the server. Hiding a button is not a permission check.
- Deleting a project hides it; the data stays. Sensitive changes are written to an append-only audit log.