Availability & regions

Where Fibric runs, and how well.

A plain account of where the platform is hosted, the uptime we hold ourselves to, where your tenant data lives, and what kind of support each plan can expect. No invented numbers. When we are not sure, we say so, and you can always check the live state on the status page.

All systems operational View live status →
Regions

Hosted in the US first.

We run where we can run it well. Today that means United States regions, with additional regions opened on request as customers need them.

RegionScope
LiveUnited States (East)Primary region
Platform, connectors, products, and tenant data. This is where Fibric runs today and where new tenants are provisioned by default.
LiveUnited States (West)Failover & latency
Used for resilience and to keep response times low for West Coast operations. Same governance, same tenancy walls as the primary region.
On requestEuropean UnionData residency
For teams that need EU data residency. We will talk through scope and timing with you rather than promise a date we have not committed to.
On requestOther regionsWhere you operate
Operating somewhere else and need Fibric close to it? Tell us where, and we will scope a region against real demand.

Regions are infrastructure, not a vertical list. A tenant lives in exactly one home region; nothing crosses a region boundary unless you ask for it. To open a new one, start a request.

Uptime posture

A target we hold, not a promise we dress up.

We design and operate the platform to a high-availability target. We report the real numbers on the status page rather than quote a guarantee we have not earned the operating history to back.

99.9%Availability target
Single-flightPer entity, fail-closed
LiveState on status page

The target is a target, not a contractual figure. What actually happened, uptime, incidents, and response times over recent windows, lives on the status page and is the number we stand behind. Because every action is single-flight per entity and idempotent, and trust fails closed rather than open, a degraded dependency stops work safely instead of flooding a downstream system.

Data residency

Your data stays in your region, and behind your wall.

Tenant data is stored in the home region you are provisioned in and is not moved out of it unless you ask. There is no shared pool where one customer's records sit next to another's by accident.

Isolation is enforced in the data layer itself. Every envelope and every row carries a reseller_id and a tenant_id, and the database refuses to return rows that do not match the caller's tenancy. The wall is structural, not a filter we remember to apply, so a query can only ever see one tenant's data.

Every action a Fibric operator takes also writes an attributable, reversible receipt, so you can read exactly what happened, in which region, on whose behalf. Real data only goes in, and a placeholder is never allowed to pass as a governed metric.

For the full picture, including how trust fails closed and how receipts work, read the trust page.

Support & SLA posture

Different plans, described in words.

Higher plans get faster, more committed support. We describe that posture in plain language here; firm response commitments are set in your agreement, not on a marketing page.

Starter

Get up and running

  • Email and docs support during business hours.
  • Same governance and tenancy walls as every other plan. Trust is not a paid tier.
  • Status page and incident notices, the same view we use internally.
  • Best-effort response, with no firm SLA attached.
Growth

Operating in earnest

  • Priority support with committed response targets during business hours.
  • A named contact for onboarding new systems and operators.
  • Heads-up on maintenance windows that could touch your region.
  • Response commitments written into your agreement.
Scale

Mission-critical operations

  • The fastest response posture we offer, including extended-hours coverage.
  • A direct line for incidents and a review of your availability needs.
  • Region and residency requirements scoped with you directly.
  • Formal availability and support terms negotiated in contract.

Plans, what is included, and where the platform is free are laid out on the pricing page. Exact response times and availability terms are agreed in writing, not implied here.

Get started

Tell us where you operate. We will run close to it.

Early access is open. Connect a system, set an intent, and go live in your region, governed from the first action.

Get early access → Check live status →