Cloud · Platform

JJ Forge

The AI-native build platform: a multi-tenant reference architecture with row-level security, an agent scaffold, and CI green before the first feature exists.

Scope a Forge build

Cloud Envision Accelerate

What it is

JJ Forge is the reference build every platform we ship starts from: a multi-tenant Postgres schema with row-level security on every table, an agent scaffold, and a pipeline that was green before the first feature was written. You are not paying us to decide where the tenant boundary goes — that is settled, tested, and the same on your build as on the last one. What varies is your domain model, your workflows and your integrations.

Reference architecture

What the platform is actually made of. You can read this before you sign anything, and you own it afterwards.

01Next.js App RouterReads in React Server Components, mutations in Server Actions with a Zod schema at the boundary. No provider key reaches a browser bundle.
02Postgres with RLSEvery tenant row carries org_id, set and frozen by trigger. Policies are one indexed equality, deny by default, with a positive, negative and privileged test per table.
03Event spineA mutation writes its row and emits a domain event; handlers subscribe. Each is idempotent on a natural key and dead-letters after five attempts, so a retry cannot bill twice.
04Job workerWebhooks, embeddings and scheduled jobs run in Edge Functions as job_worker, never as service_role. pg_cron schedules them, and every webhook is recorded before it is processed.
05Agent scaffoldAn agent is a registry row, a versioned prompt, a typed tool set and at least three golden eval cases. Autonomy is enforced by which tools exist, not by prompt wording.
06Delivery pipelineA preview deploy per pull request, with lint, types, unit tests and the RLS suite as the merge gate. A new table without a policy test fails the build.

What you get

A running multi-tenant application on your own Supabase project and Vercel account, owned by you from the first commit.
Schema, migrations and RLS policies in your repository, with a positive, negative and privileged policy test for every table.
CI on every pull request — lint, types, unit tests, the RLS suite — and a preview URL per branch.
Local, preview and production environments configured, with secrets in a manager rather than a file in the repository.
A runbook: how to add a table, add an agent, roll back a deploy, rotate a key.
Two weeks of pairing with your developer after handover, or a retainer if you do not have one yet.

What it costs

Published bands with their assumptions. A platform page without one is a draft and does not publish.

Published price bands and the assumptions behind them
Band	From	What it buys	Typical duration	Assumes
Foundation	₹6,00,000	The reference build on your infrastructure: auth, roles, multi-tenant schema with RLS, CI, and one workflow running end to end.	4–6 weeks	One tenant model and up to three roles Your Supabase and Vercel accounts, billed to you directly Screens composed from our component library, not a new visual system No migration of data out of an existing system
Platform	₹18,00,000	A production platform: your domain model, the workflows around it, role dashboards, integrations, and the event spine behind them.	10–14 weeks	Scope fixed by a two-week Envision engagement, credited against this band Up to four third-party integrations with documented APIs One named decision-maker available weekly to approve or reject Payment and messaging provider accounts opened in your name
Delivery pod	₹4,80,000 per month	A standing pod — engineer, part-time architect, part-time designer — shipping fortnightly against your backlog.	3-month minimum	The backlog is yours; we do not also run your product management Fortnightly releases, demonstrated rather than reported Thirty days' notice to stop after the minimum term Out-of-hours on-call and incident response priced separately

Where it has run

120 staff

The carts that used to just leave

A grocery group's online checkout was losing more baskets than it converted. Rebuilding it recovered nearly a quarter of them.

23% target recovery of abandoned baskets within eight weeks

60 staff

Reports that stopped needing a chase

A diagnostics lab cut report turnaround from three days to four hours by fixing the handoffs, not the analysis.

4 hours target report turnaround, against a three-day baseline

210 staff

₹1.4 crore of margin nobody could see

A third-party logistics operator found out which of its lanes actually made money, two weeks after starting to look.

₹1.4 Cr annual margin leakage a lane-level model is designed to surface

72 staff

A security review answered in an afternoon

An accountancy practice stopped losing three weeks per client to evidence-gathering by making the trail a by-product of the work.

4 hours target time to answer a 90-question security review

40 staff

Six days to publish a listing, down to nine hours

An estate agency stopped waiting on a photographer and a copywriter to get a property live.

9 hours design target from instruction to live listing

55 staff

Every recommendation carrying its reasoning

An advice firm made the suitability basis a by-product of giving advice rather than a document written afterwards.

100% of recommendations carrying a cited suitability basis

Would Forge fit your work?

Tell us what the business needs to do differently. If this platform is not the answer we will say which one is, or that the honest answer is none of them.

Scope a Forge build