Project tracking that doesn't leak.
Kanban and sprint, custom statuses, dependencies, in-app discussion, attachments. The milestone state machine runs from pending through achieved.
Projects, milestones, time, billing, capacity, audit — and the people who do the work — in one tightly-tuned workspace. Built by JBS for the way a software services firm actually ships.
Stratum is the operating system JBS built to run JBS. Every client, every project, every milestone, every billable hour, every cron run — surveyed and recorded in one place, by the people who depend on it being right.
It replaces the stack of half-fitting tools that most services firms cobble together — a project tracker here, a timesheet app there, a billing spreadsheet somewhere else, a permissions matrix that nobody trusts. Stratum is the single source of truth across all of it.
Built on the technology stack JBS uses every day — TypeScript end-to-end, NestJS on the server, React on the client, PostgreSQL underneath, AWS-hosted, Argon2id auth, append-only audit log. One tenant per customer. Nothing shared between firms.
Kanban and sprint, custom statuses, dependencies, in-app discussion, attachments. The milestone state machine runs from pending through achieved.
One timer per work item. Stopped on the server, not the tab. Survives client crashes, lid closes, network hiccups. Audit-only — no approval gate.
Billable-by-task-type rules. AMs, PMs, and the CTO can pull a draft any time. A cron drafts one for every project on the first of the month.
System roles, freeform designations, manager hierarchy from reports_to. Permissions follow role. Designation is for display, not gating.
Heat-grids across the delivery team. Anomaly flags. Role-aware home dashboards — each tuned to the work that role actually owns.
Every state change, every export, every cron run, every override — recorded with the actor and source. Nothing in this system is forgettable.
The tools you trust most are the ones built by the people who use them.