Built for reliability. Designed to keep you running.
We understand how important availability is to your business. Whether you're hosting an application, managing a database, or running production workloads, Brimble is designed to provide reliable infrastructure with the monitoring, safeguards, and operational processes needed to minimize disruptions.
Our approach focuses on infrastructure resilience, monitoring, automated recovery, and transparent communication.
Our availability commitment
We target 99.9% monthly service availability for the Brimble platform on paid plans. Current status and past incidents are on status.brimble.io.
Availability is measured as the percentage of time the Brimble platform edge successfully routes valid requests to healthy customer workloads, based on external checks run every minute. A minute counts as unavailable when the platform itself (not the customer's application) fails to serve requests.
Availability may vary depending on the service, deployment configuration, region, and underlying infrastructure. On eligible paid plans, this commitment is backed by our Service Level Agreement, which covers applications, managed databases, and the dashboard, and sets out how availability is measured, what is excluded, and the service credits available if we fall short.
For higher or custom commitments, we offer enterprise Service Level Agreements.
What is not counted as downtime
- Issues caused by customer application code, configuration, or environment variables.
- Scheduled maintenance announced in advance.
- Outages of third-party services outside Brimble's control, such as DNS providers, CDNs, or upstream cloud providers.
- Workloads on free plans.
- Disruptions caused by abuse, security incidents originating from customer workloads, or events beyond our reasonable control.
How we build for reliability
Infrastructure monitoring
We monitor infrastructure health, application metrics, network connectivity, and system performance across our platform.
When we detect abnormal behavior, or a customer reports an issue, our team investigates and works to restore service as quickly as possible.
Automated recovery
Brimble uses automated health checks and workload orchestration to detect failed applications and initiate recovery.
Unhealthy application workloads are restarted or rescheduled automatically. For managed databases, our team investigates and restores service when automated recovery is not possible.
Regional infrastructure
Brimble operates compute infrastructure across multiple geographic regions, allowing customers to deploy workloads closer to their users.
Regions run on separate compute capacity and share a common control plane. Regional availability does not automatically mean applications are replicated or fail over between regions.
Data protection and backups
Managed databases that support backups are backed up automatically every hour by default. Backup schedules and retention depend on your plan, and some plans allow you to customize them.
Because backups are taken on a schedule, a restore may not include changes made since the most recent backup. Restoring a backup replaces the current contents of the database. Point-in-time recovery is not currently available.
Secure infrastructure
Reliability and security go hand in hand. We use infrastructure isolation, access controls, and operational safeguards to reduce the risk of unauthorized access and unintended service disruption.
We continually review and improve the systems that support our platform.
Incident management and communication
When disruptions occur, our priority is to identify the impact, restore affected services, and communicate clearly with customers.
- 1
Detection
Identifying abnormal behavior through monitoring, alerts, and customer reports.
- 2
Investigation
Determining affected services, regions, and causes.
- 3
Mitigation and recovery
Taking corrective action to restore normal operation.
- 4
Communication
Posting updates on our status page at status.brimble.io and notifying affected customers directly where appropriate.
- 5
Post-incident review
Reviewing significant incidents, sharing a summary with affected customers, and putting changes in place to prevent recurrence.
Customers can report service issues through Brimble Support.
Support response times
Our support team is available every day from 9am to 10pm (WAT).
Scheduled maintenance
We periodically perform infrastructure maintenance, software upgrades, and security updates to keep our platform stable and secure.
When maintenance is expected to affect customer services, we announce it in advance on our status page and schedule it to minimize disruption. Some maintenance operations may require temporary service interruptions.
Understanding service availability
The availability of an application or database depends on both Brimble-managed infrastructure and the customer's deployment configuration.
For example, applications running a single instance may experience brief interruptions during host failures, restarts, or deployments. Configuring multiple instances through autoscaling improves resilience.
Similarly, data durability, backup recovery, and high availability are distinct capabilities. High-availability database clusters and backups must be enabled for the databases that need them.
Brimble's availability target should not be interpreted as a guarantee that every individual application, database, or deployment will achieve the same level of uptime.
Enterprise reliability and custom SLAs
Organizations running business-critical workloads may require additional availability commitments and operational assurances. Brimble offers custom Service Level Agreements for eligible organizations, which may include:
- Contractual uptime guarantees and defined availability measurements.
- Service credits when agreed availability commitments are not met.
- Agreed support response times and escalation procedures.
- Infrastructure redundancy and high-availability configurations.
- Custom monitoring, incident communication, and operational requirements.
Commitments are determined based on the services involved, deployment architecture, and the terms of the agreement.
Need a custom reliability commitment?
Talk to us about your infrastructure and SLA requirements.
Transparency and continuous improvement
Reliability is an ongoing responsibility.
We continuously evaluate our infrastructure, monitoring, recovery processes, and operational practices to improve platform stability and reduce the impact of service disruptions.
Our goal is simple: provide infrastructure you can depend on, communicate transparently when issues arise, and keep improving the experience of running production workloads on Brimble.