Research
Sit with the people doing the work, find what costs them time or money, and write it down as a numbered blueprint and a decisions log.
TechZap Labs · Product & R&D
Research that ships.
Plate TZL-01 · 1,220 wellsWell —Click any well to add a sample.
We are the product and R&D arm of TechZap. We turn hard operational problems into software that runs in production — then we publish how we did it.
What’s growing
2026-10-22- Zaptra OneClientOS for Zaptra — portal, admin, APILive
- TechZap InfraOne gateway to every third-party providerLive
- Zaptra AI SitesBrief in, structured website outIn development
- FlowraBusiness automation, designed and run for youLive
- ZENTIQAgents grounded in a company’s own dataResearch
What we do
The group’s products are built here.
TechZap Solutions builds for clients. Zaptra builds brands and websites. Labs builds the platforms underneath them — products the group owns, runs and sells. We work in three modes, usually all at once.
Build
Design the domain model, the APIs and the interfaces. Java and Spring on the server, React on the client, tests against a real database.
Operate
Containers, CI/CD, TLS, backups, monitoring and on-call — plus the help centre and videos that keep support quiet.
- Java 21
- Spring Boot
- PostgreSQL
- React
- Vite
- Astro
- Podman
- Caddy
- Cloudflare R2
- GitHub Actions
- Testcontainers
- Claude
- Remotion
Featured study · 01
Live since Sep 2026Zaptra One
A ClientOS for a digital studio.
Zaptra’s clients used to find out how their website was going by asking. We built one login where a business sees every project, approval, invoice, domain and website Zaptra runs for it — and an admin where Zaptra runs the whole relationship. Portal, admin, API, emails, monitoring, help centre and films.
- Apps in production
- 3
- Lines of code
- ~99k
- Schema migrations
- 51
- Help languages
- 3
How we work
From friction to production.
Five stages, and each one grows out of the last.
- 01
Frame the problem
We start where the friction is: the WhatsApp thread, the spreadsheet, the bank slip nobody can find. Requirements come from the work, not a template.
- 02
Write the blueprint
Every product gets a numbered spec of what it is and a decisions log of why. New engineers — and AI agents — can pick it up from one page.
- 03
Build the spine
Data model and tenancy first, screens second. A clean domain model is what lets a product grow for years without a rewrite.
- 04
Ship behind tests
Integration tests against a real database gate every deploy. A merge to main is a production release, so main is always releasable.
- 05
Operate and explain
We run what we build — backups, monitoring, incidents — and we ship the help centre, the films and the study alongside the code.
The group
One group. Each company does one thing.
Labs sits in the middle: it builds what the others sell, run and grow. Zaptra One is the clearest example — Zaptra owns it, Labs builds it, TechZap Infra connects it to the outside world.
- The parent company
TechZap Solutions
Enterprise software, engineering and consulting for clients.
- Digital growth studio
Zaptra
Brands, websites and growth for businesses — and the owner of Zaptra One.
- Product & R&D
TechZap Labs
Builds and maintains the group’s products and platforms.
- Platform
TechZap Infra
Fronts every provider the group relies on: domains, email, SMS, storage, AI.
- Business automation
Flowra
Business automation, designed and run for you.
- Enterprise AI
ZENTIQ
Agents and copilots for serious business systems.
Lab notes
Six rules we build by.
Boring infrastructure, ambitious products.
Postgres, containers, a reverse proxy. Proven parts, so the novelty goes where customers can feel it.
The schema is the source of truth.
Every change is a versioned migration. Balances are derived from the ledger, never stored and hoped for.
Tenancy is not a feature.
Scoping is enforced centrally on every read and write. Another organisation’s data is a 404 — it simply does not exist.
Every manual step is a visible, timed task.
If a human still has to click, it shows up in a queue with an owner and an SLA. That queue is our automation backlog.
Document as you ship.
Help articles, videos and decision records are part of done. Software nobody can explain is not finished.
Publish the work.
We write studies of what we build — the problem, the trade-offs, the parts that are not finished yet.
Partner with Labs
Got a problem worth a product?
We take on a small number of partnerships each year — operators with a hard, recurring problem and the appetite to build something that lasts.
Start a conversation