Limited audit slots each month. The $750 audit is credited in full to a build started within 60 days. Claim your credit

  1. Home
  2. How our software is built

Engineering

The interesting decisions are the ones you cannot see.

What makes business software trustworthy is what it refuses to do at 3 am. This is how we build ours, and yours.

  • 2,842 automated tests
  • Tenant isolation in the database
  • Every integration listed by its real state

One customer's data cannot reach another's. Three times over.

Multi-tenancy is where this kind of software fails catastrophically rather than gradually, so it is defended in depth rather than once.

Every row carries the tenant it belongs to.

Necessary and nowhere near sufficient: a query that forgets the filter still returns everything.

The query layer fails closed when it does not know who is asking.

Not "returns nothing": refuses. A read with no tenant in scope is a bug, and silence would hide it.

PostgreSQL enforces it underneath both.

ALTER TABLE "Invoice" ENABLE ROW LEVEL SECURITY;
ALTER TABLE "Invoice" FORCE ROW LEVEL SECURITY;

CREATE POLICY tenant_isolation ON "Invoice"
  USING      ("tenantId" = current_setting('app.tenant_id', true))
  WITH CHECK ("tenantId" = current_setting('app.tenant_id', true));

FORCE matters: without it the table's owner is exempt, and the policy protects everybody except the account the application would most likely run as. The application connects as a role that is not the owner, so the policy actually binds.

Rules that outlive the code that wrote them

A rule in application code is a rule until somebody adds a second code path. A rule in the schema is a rule until somebody writes a migration to remove it, which is a deliberate, reviewable act rather than an oversight.

Nobody reviews themselves.

CHECK ("authorEmployeeId" <> "subjectEmployeeId")

No code path can reach around it, including one written under pressure next year.

Two patients cannot hold one bed at the same time.

EXCLUDE USING gist (
  "bedId"                     WITH =,
  tstzrange("from", "to")     WITH &&
)

PostgreSQL refuses the overlap itself. There is no race for two screens to lose.

A task cannot be filed under another project's milestone.

FOREIGN KEY ("milestoneId", "projectId")
  REFERENCES "Milestone" ("id", "projectId")

A composite key rather than a plain one. Referencing the id alone would let a milestone from a different client's engagement be attached, and the mistake would look fine on every screen.

A retainer never bills on a date some month does not have.

CHECK ("dayOfMonth" BETWEEN 1 AND 28)

A retainer set to the 31st silently skips February, and the skipped month is the one somebody finds in March while reconciling.

It asks before it does anything it cannot take back

Automation that acts freely is a liability dressed as a feature. The gate is by class of action, not by named automation, so a new automation cannot sidestep a rule by being new.

Reversible things happen. Irreversible things wait.

Filing a CV against a job opening is reversible and happens on its own. Replying to the candidate is a message to a member of the public, so it waits for a person. It waits every time it is the first of its kind, and always for actions marked as needing a human.

Nothing is stored that a leak would make worse.

A mailbox password is read access to a company's entire correspondence. The database holds a reference to where that credential lives, never the credential, so a dump of the table hands over nothing.

2,842 tests, on every change

Suites across the engine, the workers and three interfaces, as of October 2026. They run on a clean machine with the schema built from its migrations. That is the only way to know the migrations are the truth, not a description of somebody's laptop.

1,744end-to-end, over HTTP against a real database
800unit tests on the arithmetic and rules
285interface tests across three apps
13scheduled-work tests

The end-to-end suites talk to the engine the way a browser does. They sign in, get refused when they should be, and check that one tenant cannot read another's row. A test that mocks the database cannot tell you row-level security works.

Systems we have built, and exactly what ships

Two products on one engine

We build our own products the way we would build yours, and two are live. Both are built for Indian businesses, which is why GST and Indian privacy law run through them. For clients in the US, UK, UAE and Australia we build in your accounts around your own tools; these products show how we engineer.

For clinics and hospitals

Xwits Healthcare

A clinic operating system: front desk, queue, consultations, prescriptions with allergy checks, inpatient beds, operating rooms, credentialing, revenue cycle and quality records.

A bed or an operating room cannot be double-booked, because the database rejects the second booking outright. Every patient-facing message waits for a person.

healthcare.xwits.dev
For software studios and agencies

Xwits Startups

What a software studio runs on: the standup, client engagements, the ticket board, time and utilization, retainers and bills. GitHub issues arrive as tickets, so work is described once rather than twice.

Retainer invoices are raised from the contract's own terms, and a period is billed once even if the run happens twice. The schedule that would start the run each morning is not deployed yet, so today a person starts it.

startups.xwits.dev

Every integration, and where it actually sits

Most sites publish only what works. This one publishes all of it, because the alternative is somebody finding out during a trial.

IntegrationStateWhat that means
GitHubWorkingPull requests and issues arrive by webhook. An issue becomes a ticket on the board, and closing it closes the ticket. Covered by tests.
RazorpayWorkingPayment links on the customer's own merchant account, payment webhooks, and reconciliation that reads the provider's own list back to find anything a webhook never delivered.
WhatsApp (BSP)Adapter onlyMessage policy, templates, consent and suppression are built and tested. It needs a business account with a provider before it sends anything.
Missed-call telephonyAdapter onlyInbound handling maps a missed call to an inquiry. No telephony vendor is connected.
Meta Lead AdsAdapter onlyLead payloads map correctly and are tested against fixtures. No live ad account behind it.
Email (IMAP)Never run liveReading a mailbox and routing a CV to the right opening are built and tested. It has never spoken to a real inbox, so the wire protocol is the one part unproven.
Google Lead FormsNot builtNamed in the provider list. Nothing behind it.
GST filing (GSP)Not builtInvoices are GST-correct and gap-free. Filing them with a GSP is not automated.
Video consultsAdapter onlyPatient consent, the consult record and the signed e-prescription are built. No video provider is connected, so a teleconsult cannot run yet.
Speech-to-text (scribe)Not builtA note can be drafted from a transcript someone supplies. Nothing records audio, stores it or turns it into text.
Supplier invoice readingAdapter onlyMatching an invoice to its purchase order and scoring the match are built. Reading the invoice itself is not connected, so its lines are entered by hand.
Phone line for the voice assistantAdapter onlyThe conversation logic is complete and tested. No telephony carrier is connected.
Lab and e-pharmacy partnersAdapter onlyOrders, results and the prescription handover run against stand-in adapters. No lab system or e-pharmacy partner is connected.
ABDM (India health records)Sandbox onlyConsent, care contexts and record assembly are built. Calls to the national gateway are simulated, and it is not certified.

This table is about our own products. Automations we build for clients use providers connected in your accounts, and each quote names them.

Four things worth being explicit about

There is no marketing module.

The engine has twelve modules and marketing is not one of them. A webhook client exists for receiving events from a marketing system; that is the whole of it.

Scheduled jobs are written but not running.

Seven jobs are built and tested: retainer billing, marking invoices overdue, expiring approvals nobody answered, the morning summary, the weekly money note, the inbox sweep and a duplicate-customer scan. Production has nowhere to run them yet, so none of them happens on its own.

Drug-interaction checks cannot fire yet.

Allergy checks work: a prescription for a recorded allergen is refused, naming it. Interaction, dose and contraindication checks read from a clinical knowledge base that is not loaded in production, so today they find nothing to flag.

There is no anomaly detection on a business's numbers.

Nothing watches revenue, payments or bookings for a slow month or a missed payment. The clinic product does flag stock: batches near expiry, unusual use and stock-out risk. Beyond that, a kit can declare which anomalies a trade would want watched. Those are keys in a list; no detector is written. The engine's own source says so:

anomalyRules → keys only; the detectors are not written

Treat the second group as design intent with a plan attached,
never as behaviour, and do not cite it to anyone as something
the product does.

Because the alternative costs more

A capability listed but not built costs a sales call, a trial, and the trust of somebody who found out themselves. Naming it costs one paragraph.

It is the same discipline the software is built on. A schema that refuses an impossible row and a site that refuses an unearned claim come from the same instinct. A company that tells you what its software can't do can be believed about what it can.

The right amount of AI

Ready to put your daily business operations on autopilot?

Stop losing valuable revenue to missed inquiries and back-office admin. Book a 30-minute feasibility call to see what your custom AI system looks like.

Fixed pricing · 100% client-owned systems · Pay at wholesale API cost

Book a 30-minute call.

Pick a time that suits you. The video link arrives with your confirmation.

Loading the calendar…

Calendar not loading? Open it in a new tab, or write to hello@xwits.dev.