Rewrite of the project-based ERP I built and ran at ADM for a decade, this time as a multi-tenant SaaS: projects, timesheets, invoicing, expenses, HR, and reporting on Bun and React.
The problem
After ten-plus years running the original Intranet on Ruby on Rails, I learned a lot about what fit a project-based business and what was a compromise that calcified. Time to start fresh, with the workflow modeled right from the data layer up.
What I built
Bun + Hono API over Drizzle and Postgres, React 19 with TanStack Query on the front. Every module is composed from a set of arc primitives: base models, fail-closed authorization policies, approval-workflow state machines, CRUD and workflow hooks, and shared UI components. Signup, org creation, member invitations, and Stripe per-seat billing are built in.
Where it is now
Active development. No public release yet.
A project-based ERP with the workflow modeled into the data layer from day one, and self-service orgs with per-seat billing on top.
Made with Bun, Hono, Drizzle, Postgres, React 19 and Stripe.