Components
We track the operational state of seven subsystems. Today this is a manual attestation — V1.5 will replace it with automated probes against every component.
- Operational
Marketing site
kaydenconnect.com
Public website, blog, pricing, and lead-capture forms.
- Operational
Application
app.kaydenconnect.com
Tenant SaaS application: feed, spaces, members, settings, billing.
- Operational
Authentication
Firebase Authentication
Sign-in, session cookies, SSO with Google and Microsoft.
- Operational
Data Connect / PostgreSQL
Cloud SQL (PostgreSQL 17) · europe-west1
Primary application database: posts, spaces, members, billing records.
- Operational
Stripe payment processing
Stripe
Subscription billing, plan changes, invoices, and tax computation.
- Operational
Email
Resend · Loops
Transactional email (Resend) and marketing email (Loops).
- Operational
Push notifications
Firebase Cloud Messaging
Browser and mobile push for mentions, replies, and announcements.
Status reflects the last manual review on . If you are seeing degraded behaviour right now, please contact support@kaydenconnect.com — we will update this page once the issue is confirmed.
Region & data residency
All customer data is stored in Google Cloud’s europe-west1 region (St. Ghislain, Belgium). This includes Cloud SQL (PostgreSQL), Firebase Authentication, Firebase Storage, and Cloud Run compute. Primary customer data is not replicated to other regions.
A small number of operational sub-processors (Stripe, Resend, Loops, Firebase Cloud Messaging) operate from the United States or globally. The full list, with processing region for each sub-processor, is published at /legal/sub-processors.
Incident history
No incidents reported. Kayden Connect is in launch phase as of . We will publish past incidents on this page once V1.5 ships, including: timestamp, affected components, customer impact, root cause summary, and remediation. Until then, customers on the HQ tier receive direct email notification of any incident affecting their tenant.
SLA & uptime targets
Our uptime commitment depends on your subscription tier. We do not publish historical uptime percentages — we have not yet collected enough operational data to make those numbers meaningful, and we will not fabricate them.
| Tier | Uptime commitment |
|---|---|
| Spark | Best-effort — no contractual SLA |
| Command | Best-effort — no contractual SLA |
| HQ | 99.9% monthly uptime target — contractual SLA with service credits by written agreement |
| Enterprise (1,000+ seats) | Negotiated — contact sales |
Full HQ SLA terms — including how downtime is measured, exclusions for scheduled maintenance, and the service-credit schedule — are published at /legal/sla.
Incident notifications
We are building an opt-in incident-notification mailing list as part of V1.5. Until then, the channels below are the official sources of incident information:
- HQ tier customers: direct email to your tenant administrators
- All customers: updates posted to this page
- Urgent issues: support@kaydenconnect.com
Subscribe to incident updates
Coming soon — subscribe via Status page V1.5
Urgent issues
If you are experiencing an active outage or security incident affecting your tenant, contact support@kaydenconnect.com with the subject line “URGENT”. Include your tenant name, the affected feature, and the approximate time the issue began. We will respond as quickly as possible — response targets by tier are documented in our SLA.
For suspected security vulnerabilities (not customer-impacting incidents), follow the coordinated-disclosure process on our Security & trust page.