Extant 2000: Building a Product Family Solo
How one person maintains hosting, HR, CRM, e-sign, accounting, and more.
Extant 2000 is the umbrella over a family of products, and I build all of them myself. The list covers hosting, HR, a CRM, systems engineering, e-signatures, accounting, a helpdesk and more. One person shipping that much sounds like a mistake. It works because the suite products share almost everything underneath them.
The family
The foundation is Hitt Hosting, which sells cloud, web and email hosting. On top of it sits a business suite, and every product in it has its own site. Here is what each one does, as the Extant 2000 front page describes it:
| Product | What it does |
|---|---|
| Hitt HR | People operations, payroll and team management |
| Hitt CRM | Customer relationships, pipeline and deal tracking |
| Hitt SE | Regulated systems engineering, from concept to closeout |
| Hitt Security | Threat monitoring, access control and compliance |
| Hitt Sign | Legally binding e-signatures and document workflows |
| Hitt Books | Accounting, invoicing and financial reporting |
| Hitt Desk | Helpdesk, ticketing and customer support |
| Hitt Field | Jobs, dispatch, quotes and invoicing for small field crews |
Hosting plus those eight makes nine apps in the suite. Beside them are products with their own domains: Hitt Fitness, Hitt Kitchen, Shepherd for faith communities, Flamenet with its forums and webrings, Flamenet Messenger for encrypted messages, Caelum for observatories, and Leanwise, which reads public FEC and lobbying records. The Extant 2000 site gathers all of them under one roof.
One foundation under every product
Every product in the suite starts from the same place: a common auth and data layer and one deployment pipeline. A new suite app is a new app on rails that already exist. It is not a new stack.
The data side is concrete. A single Postgres server holds a separate database and a separate role for each app, so one product cannot read another’s tables, and one backup job covers all of them. I described that layout in A whole SaaS suite on one box. The deploy path is shared the same way, which means a fix to how I ship one product is a fix for all nine.
A shared component library does the same job on the screen side for HR, CRM, Books, Desk, Sign and Field. Navigation, tables and forms look and behave the same from one of those products to the next. I build each of them once, and the six inherit them. A person who learns Hitt Desk already knows how to move around in Hitt Books.
One box, many fronts
Every product runs as a container on the same infrastructure, and each one is routed by its hostname. A request for the helpdesk and a request for the CRM arrive at the same front door and go to different containers. Adding a product means adding a service and a subdomain, then pointing DNS at the box and opening the hostname to confirm the certificate. It does not mean provisioning a new server and learning how to run it.
The front door is Traefik. A container gets five labels: enable routing, a host rule, an entrypoint, a certificate resolver and a backend port. Plain Traefik walks through that setup and the defaults I changed. Because one proxy sees all traffic, one set of logs shows how a request reached any product.
Sharing a front door has a price. One proxy and one box mean one place that can fail, so the hardening and the restore tests matter more than they would across separate hosts. I accept the trade because it keeps the operating surface small enough for one person to run, and when load grows I add memory and CPU to the machine before I consider a second one.
Not everything gets the same trust. Workloads I do not control sit in separate network lanes with their own egress rules, apart from the suite’s own apps. The suite shares a front door and a database server, and the isolation lives in the per-app databases, roles and lanes.
Boring on purpose
The only way I can hold this much surface area alone is to be strict about consistency. Same patterns, same libraries, same conventions in every product. Moving from the invoicing code in Books to the signing code in Sign should cost me minutes of context, not a day of relearning.
That rule decides where my attention goes. The plumbing is deliberately uniform, so my effort goes into what each product does for its users: legally binding signatures in Sign, regulated engineering work in SE, dispatch and quotes for small crews in Field.
A shared foundation also makes some work cheaper than it looks. When I improve the sign-in flow once, nine apps get it. When I tighten a check in the deploy path, nine apps pass through it. The cost of the family grows slower than its size because most of that cost is paid once.
The wider project is bigger than the suite. First steps into the Extant 2000 world covers the 3D office where each product has a desk.