What is OctaneCare, exactly?

OctaneCare is the name for our Operate & Run retainer — an ongoing, tiered plan that keeps your production Rails app maintained, monitored, secure, and improving. It's the productized version of "we stay involved": a defined service with a named engineer, not an ad-hoc "we'll get to it" arrangement.

Do you only maintain apps you built?

No. We take on inherited apps too — the first step is mapping the codebase properly so we operate it as confidently as one of our own. Apps we built are the smoothest handoff, but a well-built Rails app from another team is absolutely something we can run.

How is this different from a support contract?

A support queue reacts to tickets from people who don't know your code. This is continuity: the same engineer who understands your platform watches it, keeps it current, and keeps shipping to it. We hold your app to the same on-call standard we hold our own production SaaS — because that's literally how we run our own business.

What do you actually monitor?

Errors via Sentry, uptime, and performance — with dependency and security updates on a regular cadence so nothing rots into an emergency. The goal is that problems surface to us before they surface to your users, and that "we've been meaning to update that" never becomes an incident.

Can I combine this with new feature work?

Yes — incremental feature work is part of the retainer, not a separate engagement. The higher tiers include more room to keep shipping the roadmap. For a large new capability we'd scope it like a build, but steady, ongoing improvement is exactly what OctaneCare is designed for.

Retainer

OctaneCare

Operate & Run — we keep your app running on the same on-call standard we hold our own products to. No hand-off, no disappearing act.

OctaneCare is our Operate & Run retainer for production Rails apps: maintenance, monitoring, security and dependency updates, incremental feature work, and error triage, from the engineer who actually understands your code. It's for anyone with a live app — built by us or inherited — who needs it kept healthy and moving forward by a person, not a rotating support queue. We operate our own portfolio of production SaaS on this exact standard, including the 2 a.m. pager. Yours gets the same.

What problem does this solve?

Your app is live, and now it's nobody's job. Dependencies drift out of date, security patches pile up, small bugs go unfixed because everyone's busy, and the roadmap stalls because there's no one to ship it. The alternative on offer is a faceless support queue that doesn't know your code and treats every ticket like the first. What you need is continuity — someone who understands your platform, watches it, keeps it current, and keeps it improving — without you having to hire and manage a full-time engineer to do it.

How we approach it

1. Learn the platform end to end — if we built it, we already know it; if we inherited it, we map it properly first. 2. Put monitoring in place — Sentry for errors, uptime and performance watched, so problems surface before your users find them. 3. Keep it current — regular dependency and security updates, so debt never piles into an emergency. 4. Triage and fix on a real standard — the same on-call discipline we run our own products on. 5. Keep shipping — incremental feature work so the platform improves, not just survives. A named, tiered retainer, not ad-hoc "email us if it breaks."

What you get

- Ongoing maintenance and dependency management - Error monitoring and triage (Sentry) with real response, not just alerts - Uptime and performance monitoring - Regular security and dependency updates - Incremental feature work — the roadmap keeps moving - Deploys handled for you (Kamal) - A named point of contact who knows your codebase — no rotating queue - Tiered plans matched to your platform's size and needs

How long does it take?

An ongoing monthly retainer, tiered to your platform's size and needs. Month-to-month continuity, not a long lock-in.

We don't build and vanish

The most common thing that goes wrong with custom software isn't the build — it's the silence after it. The team that wrote it moves on, and your live app slowly becomes a liability nobody owns.

OctaneCare is the opposite arrangement. The person who scoped and wrote your platform is the person who keeps it running. One point of contact, zero handoff, no sales-then-disappear.

We hold your app to the standard we hold our own

This is the offering our "we run our own in production" advantage sells better than any other, because it's not a promise — it's our daily job.

Octane operates a portfolio of its own production platforms — self-hosted on Hetzner via Kamal, running the full Rails 8 Solid stack, with Sentry for errors, rack-attack for abuse protection, and Cloudflare in front. We run our own on-call. When something breaks at 2 a.m. on one of our products, we're the ones who get paged and fix it.

Your platform gets that same standard: watched, patched, and improved by someone with real production discipline and real skin in the game.

Named and tiered, not "email us if it breaks"

The shops that do this well productize it — CodeCare, OpsCare, a Rails maintenance retainer with clear tiers. OctaneCare does the same: a defined service with a named engineer and plans matched to your platform's size, so "we stay involved" becomes something you can actually buy and rely on. Priced per engagement and scoped to what your app actually needs — not an off-the-shelf tier you force-fit. Month-to-month continuity, not a long lock-in.

Frequently asked questions

What is OctaneCare, exactly?: OctaneCare is the name for our Operate & Run retainer — an ongoing, tiered plan that keeps your production Rails app maintained, monitored, secure, and improving. It's the productized version of "we stay involved": a defined service with a named engineer, not an ad-hoc "we'll get to it" arrangement.
Do you only maintain apps you built?: No. We take on inherited apps too — the first step is mapping the codebase properly so we operate it as confidently as one of our own. Apps we built are the smoothest handoff, but a well-built Rails app from another team is absolutely something we can run.
How is this different from a support contract?: A support queue reacts to tickets from people who don't know your code. This is continuity: the same engineer who understands your platform watches it, keeps it current, and keeps shipping to it. We hold your app to the same on-call standard we hold our own production SaaS — because that's literally how we run our own business.
What do you actually monitor?: Errors via Sentry, uptime, and performance — with dependency and security updates on a regular cadence so nothing rots into an emergency. The goal is that problems surface to us before they surface to your users, and that "we've been meaning to update that" never becomes an incident.
Can I combine this with new feature work?: Yes — incremental feature work is part of the retainer, not a separate engagement. The higher tiers include more room to keep shipping the roadmap. For a large new capability we'd scope it like a build, but steady, ongoing improvement is exactly what OctaneCare is designed for.

Related work

Wildcat Off Road Park: A Custom Booking-and-Payments Platform for a Multi-Accommodation Off-Road Park

A custom Ruby on Rails reservation-and-payments platform for a Kentucky off-road park that rents cabins, RV sites, and campsites. One booking engine handles both customer self-service and staff-created reservations — date-lock availability that prevents double-booking, Stripe deposits and balances, group bookings for multi-trailer trips, damage charges on a card on file, policy-driven refunds, and an operations reporting hub — live at wildcatoffroadpark.com.

Ready to talk about OctaneCare?

Tell us about your project and we'll help you figure out the right starting point.

Start a project