Do you want pre-built SDKs — or not?

ProjexLight generates a complete app either way. Reusing ProjexCloud's SDKs is an opt-in accelerator, not a requirement. This page lays out both sides honestly so you can pick per project — and change your mind on a later export without touching existing code.

Accelerated — reuse ProjexCloud SDKs

useProjexCloudSdks: true · you have a ProjexCloud tenant

Ship in minutes, not weeks — a CRM, auth, scheduler, billing already exist as APIs; you skip generating the backend.
538 production-grade APIs across 9 domains, already tested and documented.
Compliance is enforced for you — identity, row-level security, ABAC/ReBAC, and consent run at the SDK gate, not re-implemented (imperfectly) in generated code.
Metered, audited, replayable — every call is billed per method, recorded in the audit chain, and traceable end-to-end.
Nothing to maintain — no backend of your own to patch, scale, or secure; upgrades ship behind the same API.
Canonical-ID data model — no duplicated identity/PII in your app; single source of truth.
Multiplies the AI-builder savings — reusing a whole SDK beats generating it (−50% tokens is just the baseline).

Standalone — generate everything

useProjexCloudSdks: false · the default · no account needed

Full control of every line — your own schema, your own endpoints, no external contract to follow.
No ProjexCloud account or runtime dependency — the generated app stands entirely on its own.
No per-call metering — you run your own infra on your own cost basis.
Best for offline-only or air-gapped apps that can't reach a hosted gateway.
Best when the app is intentionally self-contained — a prototype, a demo, or a system you must own top to bottom.

You build & maintain auth, CRM, scheduling, billing… yourself.
You own the compliance surface (identity, RLS, consent) — and its bugs.

The savings, quantified

Measured across real AI generation sessions (ProjexLight baseline) — reusing SDKs compounds these because the backend isn't generated at all:

2–6 wk → minonboarding time

−50%total tokens

−84%startup overhead

~50%fewer sessions

100% → 0%edit failures

Decision matrix

Choose…	When your situation is…
Reuse SDKs accelerated	You're building a real product fast · you need identity/CRM/scheduling/billing/consent · compliance matters · you'd rather not run and secure a backend · you're already a ProjexCloud tenant.
Go standalone default	The app must be fully self-contained · it runs offline/air-gapped without ProjexCloud · you need total control of the stack · it's a throwaway prototype · you don't want a runtime dependency or per-call metering.
Mix common	Reuse ProjexCloud for the commodity backends (auth, CRM, notifications) and generate only your differentiated domain logic and UI. This is what most teams land on.

What each SDK family gives you (if you reuse)

Domain	SDKs · APIs	You skip building…
Identity & Access (AIM)	6 · 55	login, sessions, personas, API keys, the whole six-layer identity model
Governance, Consent & Security	10 · 56	consent receipts, ReBAC, policy, DSAR/data-rights, secrets vault, audit chain, approvals
CRM & Engagement	8 · 68	contacts, deals, lead scoring, campaigns, tickets, content, events
Outreach & Communication	8 · 111	multi-touch sequences, booking/scheduling, deliverability, notifications, voice, handoff, incidents
AI & Agents	7 · 53	agent runtime, multi-LLM gateway, MCP bridge, semantic/ontology, search
Billing, Metering & Analytics	4 · 16	usage metering, invoicing, payments, analytics
Platform & Multi-Tenancy	20 · 133	tenants, workflow, webhooks, feature flags, media, geo, devices
Connectors & Integration	1 · 18	the framework to reach Salesforce/Slack/M365/Snowflake
Native HDK (mobile / edge)	11 · 28	camera, map, measure, scanner, offline sync

You can always change your mind. The choice is a single flag (useProjexCloudSdks) in your export config. Flip it on a later export to add or drop the SDK catalog + reuse rule — your already-generated code is never rewritten.

How the choice actually works

When you opt in, your CLI export bundles the machine-readable SDK catalog (mcp-server/data/sdk-catalog.json) and a reuse rule in the build instruction. During code generation the AI builder consults the catalog and, for each capability, decides reuse-vs-generate — reusing a ProjexCloud SDK (a gateway call with your tenant JWT) whenever one covers the need, and generating custom code only for the gaps. When you opt out, none of that ships and the builder generates everything, exactly as it does standalone.

← Back to the Developer Hub Browse the API Reference ↗ Agent Cookbook ↗

ProjexCloud · Developer Hub · v3.1