Workspaces, Billing, Scaling, Custom Domains, Variables
February 24 - March 13, 2026 (7 workdays)
Features and improvements built since the initial development sprint. 14 workdays total from first commit to current state.
Multi-tenant workspaces
Lucity now supports multiple workspaces per instance. A workspace is the tenant boundary: it owns projects, environments, and members. Workspace context is carried in the JWT token, and Kubernetes namespaces are discovered via lucity.dev/workspace labels.
Billing and pricing
The Cashier service handles billing through Stripe integration. Two plans are available (Hobby at EUR 5/month, Pro at EUR 25/month), each with included credits for resource usage. Resources are metered continuously with usage-based pricing across two resource tiers: ECO and PRODUCTION. See billing for details.
Scaling
Services support both manual replica counts (1-20) and horizontal pod autoscaling (HPA) with configurable min/max replicas and target CPU percentage. Scaling is per service per environment. See scaling for details.
Custom start commands
Override the auto-detected start command for any service. Useful for running migrations before startup, using a specific binary in monorepos, or customizing the entrypoint without modifying source code.
Custom domains
Add custom hostnames to services with automatic DNS verification and TLS certificate provisioning. Each service also gets a platform-generated domain (e.g. api-production.lucity.app). Custom domains map to Gateway API HTTPRoutes and survive ejection.
Resource tiers
Environments can be configured with either ECO (shared, lower cost) or PRODUCTION (dedicated, higher performance) resource tiers. The tier determines per-unit pricing for CPU, memory, and disk.
Environment variables
Full variable management with four types: shared variables (applied to all services), service variables (scoped to one service), database references (auto-injected CNPG credentials), and service references (internal DNS addresses). See variables for details.
Workspace suspension
Workspaces with payment failures are automatically suspended. Suspended workspaces restrict mutations while allowing read access and billing operations (plan changes, payment updates). Workspaces resume automatically once payment is resolved.