A car-rental marketplace, built by one engineer and an agent team.
RentPilot connects travellers in Baku with verified rental companies. I built it alone: Claude Code agents work from specs in isolated worktrees, and every change passes a review gate I own.
- Role
- Founder and sole engineer
- Timeline
- Since 30 Apr 2026
- Stack
- Next.js, NestJS, GraphQL, Postgres
- Gate
- Spec → agents in isolated worktrees → my review
- Tests
- 21 end-to-end specs, including checkout and 375px
- Status
- Live, payments switched off rentit.mobi

The problem
Rental companies in Baku take bookings in WhatsApp threads and keep them in paper notebooks. A traveller landing at the airport can't compare prices, can't see the deposit before paying it, and can't tell whether the car's papers are in order.
RentPilot gives each company a console for its fleet, bookings and payouts, and gives travellers one place to search verified companies, in Azerbaijani, Russian or English.
Constraints
One engineer
Everything else is agents, so the process has to catch their mistakes, not my memory.
Many companies, one database
A company must never see another company's bookings, even through a bug in my code.
Three languages from day one
Azerbaijani, Russian and English in the product, the emails and the contracts.
Money waits for sign-off
Payments, identity checks and e-contracts can't go live until the vendors and lawyers agree.
A pipeline that doesn't trust its engineers
Spec
Every task is a file with acceptance criteria. No criteria, no work.
About 480 tasks, 200+ done; about 40 ADRsAgents
Eleven agent definitions; nine specialists do the work, each task in its own git worktree off
25 task worktrees at oncedev.Gate
Nothing merges until it passes my review. A hook checks each task's review record before a pull request opens.
Over 200 merged pull requestsCI
Nine workflows: tests, end-to-end, image builds, security scans and deploys.
21 Playwright specs, from checkout to 375pxProduction
Hetzner behind Traefik, managed Postgres, Cloudflare R2. The API connects as a role that can't bypass row-level security.
Enforced since 9 Aug 2026
Three locks on every company's data
Agents write most of the queries, so no single layer is trusted to keep tenants apart.
- In the query
Every query carries the company's ID.
- In the client
A database-client extension adds the tenant scope and throws when it's missing, instead of returning nothing.
- In Postgres
Row-level security on every tenant table, forced, under a role without
BYPASSRLS.
ALTER TABLE "Booking" FORCE ROW LEVEL SECURITY;
CREATE POLICY tenant_isolation ON "Booking"
USING ("tenantId" = current_setting('app.tenant_id'));
-- the API connects as this role, never as the owner
CREATE ROLE rentpilot_app NOBYPASSRLS;Stack
- Web
- Next.js 16, next-intl
- API
- NestJS 11, GraphQL with query depth and complexity limits
- Data
- Postgres, Prisma 7 row-level security under a restricted role
- Files
- Cloudflare R2
- Infra
- Hetzner, Traefik, GitHub Actions
- Tests
- Playwright 21 specs, including a 375px run
- AI
- None inside the product. AI builds it; it doesn't run in it.
Outcome, with receipts
RentPilot is live at rentit.mobi in three languages. It has no real listings yet: payments, identity checks and e-contracts are built and switched off until the vendors and lawyers sign off. Here is what can be checked today.
| Claim | Checked with | Checked |
|---|---|---|
| About 1,200 commits | git rev-list --count origin/dev → 1,190 | 27 Sep 2026 |
| Over 200 merged pull requests | Distinct PR numbers merged into dev → 226 | 27 Sep 2026 |
| 41 row-level security policies on 12 tables | CREATE POLICY count in the cutover migration | 27 Sep 2026 |
| Enforced in production since 9 Aug | The API's role checked live: no superuser, no bypass | 27 Sep 2026 |
| 21 end-to-end specs | find apps/e2e -name '*.spec.ts' → 21 | 27 Sep 2026 |
| About 480 tasks, 200+ done | Task files → 483; in done/ → 204 | 27 Sep 2026 |
The repositories are private, so each number names the command or document it came from and the date I checked it.
What I'd do differently
Create the restricted database role on day one. Row-level security merged on 2 July, but production kept connecting as the owner until the move on 9 August, so for five weeks the policies were there and nothing enforced them. The only reason it didn't matter is that there were no real listings yet.
Keep the specs next to the code. The task files live in a sibling repository, and one agent guide went on calling it unversioned long after it had its own history. People skim stale docs; agents follow them, so an out-of-date instruction costs more with an agent team.
Decide how you count before you quote a number. “Merged pull requests” came out as 153, 198 or 226 depending on the command. Now every number I publish sits next to the command that produced it, which is why this page says “over 200” and shows its working.