Availability & regions

Where Fibric runs, and how well.

A plain account of the deployment region we can verify today, the availability posture we use for managed deployments, and the support levels customers can contract for. This is service information, not a live monitoring feed.

Service information, not live monitoring Read the status scope →
Regions

Hosted in the US first.

The deployment we can verify today is in AWS US East. Other residency and failover requirements are scoped with each managed deployment.

RegionScope
LiveUnited States (East)Primary region
The current BearScope site, application services, and governed tenant-data path are verified in US East. Product and connector resources are confirmed for each managed deployment.
On requestUnited States (West)Residency & latency
Not a currently advertised live Fibric region. West-region residency or failover is scoped and verified before it is written into a customer agreement.
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.

Region, backup, and data-transfer requirements are confirmed during onboarding and written into the deployment scope. To request a specific residency posture, start a request.

Uptime posture

A target we hold ourselves to.

Availability objectives, incident reporting, and service commitments are deployment-specific and written into the customer agreement. The public status page is static service-scope information, not a live uptime or incident monitor.

High availabilityDesign target
Bounded controlsValidated per deployment
ManualPublic service information

We publish no uptime percentage until we have the operating history and monitoring record to support one. The current status page explains service scope but does not run automated probes. Single-flight, idempotency, and fail-closed policy reduce failure amplification; they do not replace dependency monitoring.

Data residency

Residency and access boundaries are explicit.

Live BearScope tenant data is hosted in the verified US East deployment. Any different residency, backup, or transfer requirement is scoped and documented before provisioning.

The live application sets tenant context before governed queries run, and row-level security limits tenant-owned tables at the database layer.

Where managed action execution is enabled, the supported path records the request, policy decision, and reported outcome. A reversal is a separate compensating action only where the connected system supports one.

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

Support & SLA posture

Indicative managed-support postures.

These are planning categories, not public plan entitlements. Coverage, escalation, response objectives, and incident communications are defined only in the written agreement.

Managed pilot

Evaluate and commission

  • Deployment review, maturity checks, and a named onboarding path where quoted.
  • Control and tenant boundaries documented for the evaluated scope.
  • No public free entitlement, internal-status access, or implied response SLA.
  • Any support window and incident process are stated in the pilot agreement.
Managed team

Operate a supported path

  • A named contact and agreed process for supported systems and operators.
  • Coverage windows, maintenance notice, and escalation contacts set in writing.
  • Response objectives apply only where the agreement states them.
  • Connector and region changes require review before support scope expands.
Contracted critical scope

Negotiate the operating commitment

  • Required coverage windows and escalation paths are assessed directly.
  • Availability objectives need verified architecture and monitoring evidence.
  • Region, residency, dependency, and recovery requirements are scoped explicitly.
  • Only the signed agreement creates formal service or support commitments.

Indicative planning assumptions and managed-commercial scope are laid out on the pricing page. There is no public free entitlement. Exact response times and availability terms are agreed in writing, not implied here.

Get started

Tell us where you operate. We will scope what is supportable.

Managed early access is open. We will verify the region, data boundary, connector maturity, and support posture before anything goes live.

Get started → Read service status scope →