Version 1.0 · Effective 2026-07-11

Availability and support

Who you're actually emailing

BloomOS is built and supported by SOBO Consulting LLC. Today that means Remi Sobomehin answers your email. Not a ticketing queue, not a chatbot, not a first-line agent reading from a script.

That's a real advantage and a real limit, and you should know both.

How fast we respond

Something is broken and you can't work. One business day. Sign-in failures, a page that won't load, data that's wrong, an export that won't run. If BloomOS is between you and your job, that's the priority and everything else waits.

Everything else. Five business days. Questions, requests, "how do I," feature ideas, "can you look at this."

Business days are Monday through Friday, Pacific time, excluding US federal holidays.

Bloom Flourish customers get a standing monthly session with SOBO Consulting in addition to the above, which in practice means most questions never become emails.

Uptime

BloomOS runs on Vercel and Supabase, both of which target high availability and both of which publish their own status. We build on their reliability rather than claim our own.

We're not offering an uptime SLA with financial credits. We could write "99.9%" on this page. Most vendors our size do. But an SLA is a promise backed by money, and a one-person company promising service credits it hasn't modeled is writing a check it hasn't checked the balance for. When we can back it, we'll publish it, and it'll be a number we've measured rather than a number we liked the sound of.

What we will tell you: BloomOS has run Ambition Angels' entire operation every business day since it went live. If it's down, we know, because we're using it too.

Maintenance

Deployments happen continuously and almost never require downtime. When a change does require taking BloomOS offline, we do it outside 8am to 6pm Pacific on business days, and we tell you in advance if it's expected to last more than a few minutes.

Database schema changes are applied by hand, deliberately, after review. They are never applied automatically when code ships. This is slower and it's the reason we've never lost data.

When something is genuinely wrong

If BloomOS is down or a bug is affecting your data, email hello@bloomos.org and put the word urgent in the subject. You'll get a human, and you'll get an honest read on what's happening and when it'll be fixed, including when we don't know yet.

If it's a security issue, use security@bloomos.org instead. See the security overview for what happens next.

Changes to this page

If we change a commitment on this page in a way that's worse for you, existing customers get 30 days' notice by email before it takes effect.