Who it is for
Sourcing leads who need to know who they are buying from.
What it does
- A supplier record shows where each fact came from, down to the customs line and the date it was read.
- Search the supplier base by material and certification, then open the record behind any result.
- Write a request for quotation once and send it to up to 50 suppliers from the shortlist.
How we built it
ArcLayer did the product design, the design system and the engineering. AI agents wrote code and tests against SourceBD’s design system, and a person reviewed each change before it merged.
Build note: Why every product gets its own design system
How we work on SourceBD
Five checks on every push
CI runs type checks, lint and a production build, unit tests, HTTP checks on missing supplier pages, and the Python pipeline tests.
Migrations are replayed from zero
Every migration is replayed into a fresh Postgres 16 and checked by assertion scripts. A second replay over filled data must be refused.
One person approves production
A production deploy waits for the founder’s approval in GitHub, then ships the exact commit that passed CI.
A rollback image comes first
On the server, the running image is tagged for rollback before Docker Compose builds and starts the new one.
The live site confirms the release
The deploy only finishes when the public health check reports the same commit.
The pipeline has its own tests
The Python pipeline collects source pages, reads PDFs and matches supplier names, with pytest and ruff on every change.