Platform & Architecture

One platform. Many institutions. Strictly separated.

ForgeCircle runs on a proven open stack with multi-tenancy enforced inside the database — so each institution’s data stays its own, by construction.

Tenant tables under RLS100+ security policiesPostgreSQLSouth Asia (Mumbai) regionSAML + SCIM identity

The stack

Every layer, named.

No proprietary black boxes — each tier is a mainstream, well-documented technology your team can evaluate.

Web & Experience

Next.js
React
TypeScript
Tailwind CSS

Mobile

Expo
React Native

Data & API

Supabase
PostgreSQL
PostgREST

Compute

Deno Edge Functions
Scheduled jobs

Infrastructure

Vercel
Docker
Caddy

Multi-tenancy

Isolation enforced in Postgres — not in promises.

Every protected query passes through the same enforcement chain. Application code cannot skip it.

Tenant

Every institution is a tenant. Members join through tenant-scoped memberships — never cross-tenant by default.

Permission check

Role-scoped permission checks resolve on every protected operation, server-side.

Row-level security

Postgres enforces isolation in the database itself — not in application code that can be bypassed.

Isolated data

Tenant tables carry RLS policies. One institution can never read another’s rows.

Enterprise identity

SAML 2.0 service-provider endpoints and SCIM 2.0 user provisioning are implemented in the portal’s API routes — institutions can federate their existing identity provider.

Realtime + scheduled work

Supabase Realtime pushes live updates to clients; scheduled database jobs run lifecycle, reminder and rollup work.

Connector layer

Vendor integrations, deployed and ready.

Each connector runs as an audited edge function and is activated per institutional agreement — channels switch on only when your deployment needs them.