// a software lab

We build software, and we prove it works.

CurioLabs builds and runs websites and web apps for organizations that want the care of a big engineering team: every change reviewed, tested, backed up and monitored. Everything we offer is proven in our lab first.

lab status: all systems nominal

health-check.sh
$ ./health-check.sh --all
OK4 apps live, every deploy verified
OK0 known vulnerabilities
OKbackups daily, restore tested
OKuptime + error monitoring on
OKevery change independently reviewed
Summary: 0 FAIL. Coffee levels: adequate.
$
~1.5 h from a new security advisory to every app patched and live
21 s to roll a release back, in a timed drill
44 s to restore a database from backup, in a timed drill
0 known vulnerabilities across our live apps, checked on every change

// services

What we do

Each service is marked honestly: Proven means it runs for real clients today. In the lab means we're building and testing it before we offer it.

Proven

Websites and redesigns

Fast, accessible sites with an admin your team can use, including multilingual and right-to-left languages.

Proven

Hosting, maintenance and support

Security updates the same day, daily backups with tested restores, uptime and error monitoring.

Proven

Security hardening

Login protection, safe defaults, scoped access and secrets kept out of code, checked on every change.

Proven

Domains, email and office IT

Business email on your own domain, set up properly so it lands in inboxes, with accounts in your name.

In the lab

Web apps and client portals

Logins, roles and dashboards for your customers or staff, built on the same tested foundation.

In the lab

APIs, integrations and AI features

Connecting your tools, payments through hosted checkout, and AI features with cost limits built in.

// built in the lab

What every project stands on

Before we build for you, we build it for ourselves, run it live, and break it on purpose to make sure it recovers.

foundation

One hardened base

Every project starts from the same tested foundation: secure logins, an admin your team can use, backups, monitoring and guarded releases, all switched on from day one.

reference app · live

The Showroom

Where every new capability is built and proven before a client gets it. It runs exactly like a client site, with the same backups, monitoring and releases.

proof ledger · latest release PASSED reviewed, tested, scanned 10/10 pages checked live after deploy OK backup from last night
Open the Showroom →

in the lab

Our own products

We're building apps of our own on the same foundation. They'll appear here when they're ready to show.

status: compiling

Trusted by Afghan Pashai Community, our first client site.

// how we work

The same path for every change

No change reaches your site without passing every step. If one fails, it stops, and nothing live is touched.

  1. 01PlanScope and estimate, agreed with you first
  2. 02BuildOn its own branch, never on the live site
  3. 03ReviewAn independent reviewer approves it in writing
  4. 04TestAutomated tests and security scans
  5. 05DeployGuarded release with a rollback ready
  6. 06VerifyThe live site is checked before we call it done

Our pipeline says no before it says yes.

Real lines from our release logs. When something isn't right, the release stops itself, and the live site is never touched.

deploys we refused
STOPPED before deploying: this commit is no longer GitHub's main. Nothing was changed on the server.
SKIPPED security scan failed: new advisories. Live site stays on the last good version.
SKIPPED (not a failure): a newer run will deploy.
PASSED reviewed, tested, scanned, deployed, verified live.

// the team

Every role covered, on every project

A lab organised like a large team: each role has a clear job and clear limits, and the roles check each other. Our lead engineer owns every decision and every release.

Lead engineer Approves every release. Holds every key. Your point of contact.
CoordinationPlans the work and re-checks every claim
PlatformKeeps the foundation every project is built on
Project engineeringDedicated to your project, with its full history
Security & OpsBackups, timed drills and incident response
Independent reviewNever the one who wrote the change
ResearchA weekly security watch on our exact stack
review · template #46 · a real one
CHANGES NEEDED
The failure happens on the check after the click, not the click. This fix wouldn't stop it.
→ fix reworked, new test added
APPROVE · re-review
Covers the failing line. Turned the fix off: the new test fails, as it should.

// responsible AI

AI, with the same rules as everything else

We use modern AI tools to build faster and check more thoroughly, and we build AI features for clients. Either way, the rules don't bend.

// from the lab log

A real night, not a promise

When new security warnings hit the web server every one of our apps runs on, our checks blocked any unsafe release, no site went down, and every app was patched, reviewed and live again before breakfast.

  1. 03:15New advisories published for our web server
  2. nextSecurity scan fails, releases blocked automatically, sites stay up
  3. thenPatch prepared, tested and independently reviewed, app by app
  4. 04:39First app patched and verified live
  5. 04:50All four apps patched and verified live

UTC, 15 November 2026

Have a project in mind?

Tell us what you need. We'll reply with honest options, including when we're not the right fit.

hello@curiolabshq.com