About
A small software company that builds like a large one ships.
Merply is run by engineers. We design, build and operate products end to end, with the discipline — tests, pipelines, runbooks — usually reserved for much bigger teams.
What Merply is
Merply builds software products for businesses and operates them in production: AI-enabled platforms that read and route documents, tools that turn drawings into 3D spaces, coaching systems that adapt to their users, and the public websites and infrastructure around them.
The same people who sketch the architecture write the tests, ship the code and answer when something breaks. That is deliberate: products get better when the team that builds them also has to run them.
We keep the number of projects low enough that every one of them gets senior attention, and we say no to work we would not be proud to put on this page.
How we engineer
The standards every Merply project ships with.
- 01
Tests first, always
Unit, API and browser tests are written before the implementation; coverage thresholds are enforced in CI and never lowered to get a build green.
- 02
Decisions written down
Architecture decision records, API contracts and runbooks live in the repository, so the reasoning survives the people who made it.
- 03
One pipeline to production
Every change goes through the same gates — lint, types, tests, build, end-to-end — and deploys to a test environment before it can reach production.
- 04
Security as a review criterion
Least-privilege access, hardened edges behind Cloudflare, secrets kept out of images and dependencies kept current; security findings block the merge.
- 05
Observable in production
Health checks, structured logs, backups and a rollback path are part of the definition of done, not an afterthought.
- 06
Honest about scope
We would rather ship a smaller first release that works than a large one that is late. Trade-offs are made explicit, and early.
How we work
A short loop, repeated until it ships.
- 01
Discover
We start with your goals, your users and the constraints around them, then audit what exists. You get a scoped plan with priorities and a clear first release.
- 02
Design
Architecture and API contracts are written down as decisions before code. Interfaces are prototyped against real workflows, not placeholder screens.
- 03
Build
Small increments behind a pipeline: tests first, review, continuous integration with end-to-end checks, and continuous deployment to a test environment you can use.
- 04
Run
Production on hardened infrastructure with monitoring, backups and runbooks. We stay on to measure, iterate and keep the product moving.