Network Topology
The Fabalos ecosystem operates on a strict Tiered Release Pipeline. Logic is validated in the DevLab, previewed in Staging, and only deployed to Production when it meets Zero-Failure criteria.
client.fabalos.com
Tenant: /(client-id)
● 99.9% Uptime
The Mission Critical zone. This is where your live business logic runs. Infrastructure here is redundant, backed up, and locked (Read-Only). Changes can only be pushed via CI/CD pipelines after passing Staging validation.
Access
Authorized Personnel Only
Data Safety
Automated Backups / ACID
staging.client...
Tenant: /(client-id)
● Preview Mode
The Simulation zone. Mirrors Production exactly but uses dummy data. This is where we invite you to test new automations ("Preview Mode") and break things safely before we flip the switch to go live.
Role
Client Review (UAT)
Data Policy
Anonymized / Sandbox
Internal / Localhost
Status: Volatile
The Innovation zone. This is where I test new architectures, alpha APIs, and experimental AI agents. Nothing here is promised to work, which allows for rapid iteration and "breaking changes" without risking client operations.
Multi-Tenant Isolation
Every client is assigned a unique Tenant ID. Your data lives in a dedicated, row-level secured (RLS) partition within Supabase. No other client can read, write, or even see your operational data.
Deployment Pipeline
We never "edit code on the server." Updates follow a strict DevLab → Staging → Prod path. This prevents the common "oops, I broke the site" errors typical of freelancers.