Production vs Demo: What’s Real
The honest inventory: SuiteCentral 2.0 has a dual-mode architecture where production AI and connectors coexist with demo/fixture modes. Here’s what’s real, what’s demo, and why the dual-mode design is a strength, not a weakness.
Why this page exists
The #1 question any technical evaluator asks: “Is this real production software, or is it a demo that looks like production software?” The answer for SuiteCentral 2.0 is: both, intentionally, and here’s the transparent breakdown.
Per tier1-repo-evaluation-batch (PRODUCTION-VS-DEMO-GUIDE.md, April 9 2026):
“The presence of demo/fixture modes is NOT a sign of incomplete implementation. It is a production-grade architectural pattern designed for enterprise flexibility.”
The dual-mode design enables: immediate exploration without API keys, cost-effective demos for sales/training, offline/air-gapped deployments, graceful degradation when services are unavailable, and A/B testing between providers.
AI providers — all production-ready
| Provider | Production Status | Demo Available | Badge Color |
|---|---|---|---|
| OpenAI GPT-5.4 mini (default) | ✅ Production | Yes (mock sim) | 🟢 Green |
| Claude Haiku 4.5 (Sonnet 4.6 upgrade tier) | ✅ Production | Yes (mock sim) | 🟢 Green |
| OpenRouter (multi-model) | ✅ Production | N/A | 🟢 Green |
| LMStudio (local) | ✅ Production | N/A (always local) | 🟢 Green |
| Rule-Based Engine | ✅ Always available | N/A | 🔵 Blue |
| Mock providers | Demo only | Always available | 🟡 Yellow |
Model updates: earlier sources cited Claude 3.5 Sonnet; the production environment later showed claude-sonnet-4-5-20250929 (Claude 4.5 Sonnet). Current defaults (2026-06) are Claude Haiku 4.5 (claude-haiku-4-5, with Sonnet 4.6 as the upgrade tier) and OpenAI GPT-5.4 mini (gpt-5.4-mini; legacy gpt-4 normalizes to gpt-4o).
Connectors — the honest inventory
| Connector | Status | Auth | Notes |
|---|---|---|---|
| NetSuite | ✅ Sandbox-Tested | OAuth 1.0a | Full CRUD, Squire sandbox TSTDRV2698307 verified |
| Salesforce | ✅ Production | OAuth 2.0 | Full CRUD (leads, accounts, contacts, opportunities, cases) |
| Business Central | ✅ Production | OAuth 2.0 | OData v4 with metadata-driven field catalog |
| HubSpot CRM | ✅ Production | OAuth 2.0 | Contacts, Companies, Deals, Tickets (Phase 3, Jan 2026) |
| ShipStation 3PL | ✅ Production | API key | Order fulfillment, shipments, tracking (Phase 3, Jan 2026) |
| Oracle ERP | ⚠️ Beta | Basic Auth, ORDS | Basic CRUD only; needs production hardening |
| 11 demo-only | 🧪 Demo Only | Varies | Demonstration implementations; see the upstream registry for details |
| 1 stub | 🚧 Stub | Varies | Placeholder implementation; not executable as a production connector |
Current audited partition: 18 connector implementations — 5 production-ready, 1 beta, 11 demo-only, and 1 stub. See canonical-metrics for the maintained wording. Historical sources that say “6 production connectors” predate this registry-backed classification.
The registry-backed status labels distinguish production-ready, beta, demo-only, and stub implementations. Consult the upstream connector proof cards before making live-readiness claims.
Features — what’s production-ready
| Feature | Status | Notes |
|---|---|---|
| AI Field Mapping | ✅ Production | Real AI with OpenAI/Claude/OpenRouter/LMStudio OR rule-based fallback |
| Integration Wizard | ✅ Production | Orchestrates real connectors OR fixtures |
| AI Configuration Dashboard | ✅ Production | Manages real AI provider credentials |
| Enterprise Features (BC Metadata, Delta Sync, etc.) | ✅ Production | Real implementations |
| RAG Knowledge Base | ✅ Production | 7,415 chunks indexed in real vector store |
| Help Chat Widget | ✅ Production | Real RAG-powered assistance |
| Telemetry & Monitoring | ✅ Production | Real metrics collection |
| Mock Dashboard APIs | 🧪 Demo Only | src/routes/mockDashboardAPIs.ts |
Why this matters for the evaluation
A CTO (Reuben Cook) evaluating the repo will see fixture files, mock providers, and demo-mode flags in the code. Without this document, those artifacts look like “it’s not real.” WITH this document, they’re understood as a deliberate enterprise pattern: the same codebase serves both production customers and zero-cost demo environments, controlled by environment flags, with color-coded badges so users always know which mode they’re in.
This is the document Reuben should read FIRST, before opening any source file.
Sources
- tier1-repo-evaluation-batch — PRODUCTION-VS-DEMO-GUIDE.md and CONNECTOR_STATUS.md