Pour temp 1,084.6 °C — Cu · Independent software foundry

You vibe code it.
We forge it.

The independent foundry for AI-built software. We pour new AI-native products, take prompt-built prototypes to production, and keep both alive — audited, hardened, and verified by a human who signs their name.

Run the assayBring a project

Free · Security, tests, cost, scale · Read and signed by a human

No repo yet? Bring an idea instead →

Two doors, one production line

Bring an idea, or bring a prototype. Both leave forged.

Door 01 — The Cast

Bring an idea. We pour the product.

An agent assembly line builds it: a PM agent drafts the requirements, an architect agent designs the data model, engineer agents write the code, QA agents try to break it. Every stage ends at a human gate — nothing ships unreviewed. Fixed-scope MVP sprints. Born forged: verified against the Zha Standard from day one.

PRD ⌖ → SCHEMA ⌖ → CODE ⌖ → TESTS ⌖ → DEPLOY ⌖

Door 02 — The Forge

Bring a prototype. We make it production.

Your app works in the demo and breaks everywhere else. We refactor the architecture, harden auth and secrets, build the test suite, containerize it, wire zero-downtime deploys, and cut the token bill. Specialty: Next.js + Supabase apps from Lovable, Bolt, v0, and Cursor — the stack most AI tools generate.

INTAKE → AUDIT → HARDEN → VERIFY ⌖ → SHIP

The reality check

What comes in. What goes out.

Comparison of vibe-coded input versus Zha Foundry output
Raw material — the vibe-coded inputCast metal — the foundry output
"Works on my machine" local environmentCloud-native, auto-scaling architecture
Brittle code and silent runtime failuresEngineered test coverage, verified before handover
Exposed API keys and prompt-injection riskHardened security, encryption, and proper auth
Token-bloated, expensive LLM callsOptimized model routing and semantic caching

The Forge — productized, never hourly

Three heats. Fixed scope, fixed quote.

Audit

Know where you stand

  • Full assay: security, secrets, tests, scaling, token spend
  • Prioritized fix plan, ranked by risk
  • A written report a non-engineer can read

Fixed quote with your free assay

Full Forge

Make it production

  • Everything in Harden
  • Architecture refactor and containerization
  • CI/CD with zero-downtime deploys
  • Token-cost optimization and handover docs

Fixed quote with your free assay

Foundry Care

The foundry doesn't leave.

Software rots from day one — dependencies decay, CVEs appear, costs drift. Care is a monthly subscription: our agents watch, patch, and report; a human signs every month's health check.

  • Dependencies patched
  • CVEs closed
  • Uptime watched
  • Token costs tracked
  • Monthly report, signed
Ask about Care

The production line

Five stages. Both doors. Same exit.

  1. Stage 01 — Intake & Audit

    The material arrives

    A repo link or an idea brief. We assay what exists and scope what should.

  2. Stage 02 — Blueprint

    Architect and PM agents draw the plan

    Requirements broken down, production schema designed, scope fixed in writing.

  3. Stage 03 — Assembly

    The agent loops run

    Engineer and QA agents write, test, refactor, and re-test until every assertion holds.

  4. Stage 04 — Human Review

    A person signs their name

    Every line the agents produced gets read, challenged, and approved by a human engineer.

  5. Stage 05 — Shipment

    Cast metal leaves the floor

    A running production environment, handover docs, and the option to keep us watching.

Positions

What we don't do

We don’t bill hours

Every engagement is a fixed scope with a fixed quote, agreed before work starts. The meter never runs.

We don’t ship unreviewed agent output

Agents build fast; humans decide what leaves. Every stage of the line ends at a human gate.

We don’t grade our own homework

The Zha Standard is public. Check anything we ship against it — that’s what it’s for.

We don’t do open-ended engagements

No retainers that drift, no phase twos that never end. A scope closes, the metal ships.

The Zha Standard

Our definition of production-ready, in public.

Every project leaves the foundry checked against this list — and you can check it too. That's the point of publishing it.

Security

  • No secrets in source or client bundles
  • Auth on every route, row-level security on every table
  • User input validated at every boundary

Tests

  • Behavioral coverage on every money and data path
  • Tests run in CI on every change
  • Failures block deploys, not weekends

Infrastructure

  • Reproducible builds, one-command deploys
  • Rollback plan that has actually been tested
  • Health checks and alerting wired before launch

Cost

  • Token budget known per feature, tracked in production
  • Model routing: cheap models for cheap work
  • Caching before scale, not after the bill

Provenance

  • Every module attributable: which agent built it, which human approved it
  • Dependency manifest reviewed and pinned
  • Handover docs a stranger could operate from

Zha Standard v0.1 — expands as the foundry learns

Teardowns

Every rescue gets published.

Before, after, and what it took — real repos, real failures, real fixes. The first castings are on the floor now.

Teardown Nº 001

In the crucible

Teardown Nº 002

In the crucible

Teardown Nº 003

In the crucible

The founder

A name on every shipment.

Prem Kannan, founder of The Zha Foundry

Prem Kannan

Founder · Coimbatore, India

I'm an integrated MSc Data Science student who builds AI products in Python. At Bloom Matrix I co-built Anril AI, and I write the evaluations and tests that catch regressions before users do. The Zha Foundry applies that discipline to software that was built with AI and now has to survive real use.

thezhafoundry@gmail.com

Final pour

Stop wrestling with prompt limits.

Let's turn your vibe into structural steel. Send a repo, a broken deploy, or three sentences about an idea — a human reads every message and replies within one working day.