Core Concepts

DartStream is organized around workspaces, tenants, projects, environments, subscriptions, and runtime capabilities.

Workspace and Tenant

A workspace is the user-facing organization. A tenant is the backend boundary used by DartStream services for auth, billing, entitlement checks, and application data.

Authenticated requests include:

  • Authorization: Bearer <Firebase ID token>

  • X-Tenant-ID: <active tenant ID> when a tenant-scoped service needs it

User and Role

Users belong to one or more tenants. The backend returns active and canonical role context after login so the app can apply permissions consistently.

Common roles include admin, developer, and viewer. Role coverage is still being expanded across the product surfaces.

Project and Environment

Projects group the app or game runtime you are operating. Environments separate development, staging, production, and preview behavior.

The public site positions this as a path from project setup to live operations:

  1. Create a workspace, project, environment, and plan boundary.

  2. Bind SDKs, auth, storage, billing, telemetry, and live config.

  3. Connect provider credentials through DartStream adapters.

  4. Operate entitlements, runtime events, live-ops changes, support context, audit history, and production readiness.

Subscription and Entitlements

Billing is not only a payment flow. It controls runtime limits and enabled features.

Current plan families:

  • Sandbox

  • Standard

  • Enhanced

  • Enterprise

Entitlements include limits for auth providers, database connections, storage, API calls, websocket connections, feature flags, projects, environments, team members, Flutter apps, game projects, cloud save slots, live config environments, telemetry events, AI runtime, Unity bridge, and native modules.

Runtime Services

DartStream is microservice-based. The current app talks to separate services for:

  • Auth

  • Billing and tenant entitlements

  • Platform services and enterprise requests

  • Persistence

  • Reactive dataflow

  • Experience orchestration

Feature Flags and Live Config

DartStream is not the dedicated feature flag product. IntelliToggle owns that lane. DartStream uses IntelliToggle-backed feature workflows as part of runtime operations, live config, experiments, entitlements, and app/game operations.

Current vs Roadmap

The app includes active launch flows and forward-looking product surfaces. Docs should distinguish them:

  • Active: login, membership, subscription state, dashboard, feature flag visibility, Stripe Checkout and Portal handoff, enterprise request, logout.

  • Expanding: project lifecycle, provider connection lifecycle, database/storage workflows, team invites, game services, live telemetry, AI runtime, native/Unity bridge.