M360 runs on Google Cloud with per-tenant data isolation, RBAC, and compliance-safe outreach for banking and healthcare. Here's everything your security team needs to know.
M360 is deployed entirely on Google Cloud. The application tier runs on Cloud Run — a fully managed, serverless container platform with automatic scaling and no persistent server-side state. Data is stored in Firestore, Google's globally replicated NoSQL database.
Every client is an isolated tenant. Data is namespaced in Firestore by tenant ID — no query can cross tenant boundaries by design. Firestore security rules enforce this at the database layer, not just in application code.
All authentication is handled by Firebase Auth (Google Identity Platform). Sessions use short-lived JWT tokens. Role enforcement happens server-side — the platform does not trust client-supplied role claims.
M360's outreach framework is designed around the consent and frequency rules that matter most to regulated industries. The platform tracks every communication channel per customer, enforcing opt-out and contact restriction rules automatically.
All Firestore data is encrypted at rest using AES-256, managed by Google Cloud's default encryption. No additional configuration required.
All traffic between the browser, Cloud Run, and Firestore uses TLS 1.2+. HTTPS is enforced — HTTP requests are redirected automatically.
Every write action in M360 is logged with a timestamp, user ID, tenant ID, and action type. Logs are stored in Firestore and cannot be modified or deleted by operators or agents.
Cloud Run auto-scales from zero to hundreds of instances in seconds. There is no single point of failure — each request is served by a stateless container. Firestore provides multi-region replication automatically.
We're happy to walk through architecture, data flows, and compliance specifics on a call. Bring your InfoSec team.
Schedule a Security Review Call