Frequently Asked Questions

Octane Labs is a founder-led Rails software studio that builds production web platforms — multi-tenant SaaS, internal tools, and customer-facing products — for founders and operators. What sets it apart: Octane builds and runs its own SaaS products in production, so client software is held to the same standard as software the studio depends on to run its own business. One senior engineer scopes it, writes it, and talks to you directly — no bench, no account manager, no handoff to juniors.

Founders and operators who need real software built to run for years — something that handles real accounts, payments, and integrations without buckling the day a paying customer logs in. It's a fit whether you're taking a validated idea from zero to launch, or you have a legacy Rails app that's become risky to deploy. If you need a quick brochure site or a throwaway prototype, that's a smaller, different conversation.

Most engagements start with The Diagnostic — a paid, fixed-fee review that turns your idea into a concrete plan and a scoped build, so nobody signs a blank check. From there it's a fixed-scope build shipped in small, reviewable increments you can watch land week over week, with payments and integrations wired against real provider sandboxes rather than mocked happy paths. You launch on infrastructure you own, and you decide whether Octane hands off cleanly or stays on to operate it.

There's no honest single number for "build me a Rails app" — cost depends on scope, complexity, how many integrations are involved, and the condition of any existing code. Instead of a fixed price list, Octane works in three engagement models: The Diagnostic — a fixed-fee first step that produces a plan and a scoped estimate — then a fixed-scope build with agreed deliverables, and an ongoing retainer for products that keep evolving. Every build is scoped and quoted off that first step, once the actual requirements are clear.

You get a scope and a quote, not a running meter. Work is priced against the scope The Diagnostic pins down, so you know what you're getting before the build starts. Fixed-scope engagements ship in reviewable increments toward a milestone — you see progress along the way instead of one big handoff and a surprise invoice at the end.

Rescue is almost always the better bet for an app that still makes money. A rewrite means a year where nothing new ships, a working app thrown away, and every old bug rediscovered the hard way — while your existing app already encodes things about your business no spec captures. Octane modernizes what works and pays down what doesn't in small, reviewable steps, so the app keeps earning the whole time. A rewrite only makes sense when the foundation genuinely can't carry where you need to go — and The Diagnostic tells you which situation you're actually in.

Rails is the default for new builds — current Rails 8 and Hotwire, the modern Solid stack, deployed with Kamal — because after 13+ years with it, it's usually the fastest path to a product that's maintainable for years. But the starting point is your problem, not the framework: when another stack fits the job better, Octane builds there too. Mountain Gap Coffee, for example, is built on Shopify. You won't be pushed onto Rails regardless of fit.

You own it. Rails apps deploy with Kamal onto infrastructure you control — a plain, current Rails codebase that you or any Rails engineer can pick up and run. There's no proprietary platform and no rented infrastructure you can't walk away from. Most engagements end with software you own outright.

Production, and the proof is software Octane owns and operates. ContractorLink is a multi-tenant website-and-CRM SaaS with two layers of Stripe — subscription billing plus Connect so tenants invoice their own clients. BeanLink is a wholesale platform for coffee roasters with bidirectional accounting sync to both Wave and QuickBooks. TrackWright is an offline-capable PWA driven by a single canonical geometry engine. These aren't borrowed case studies — they're products Octane built, runs, and gets paged for.

That's your call, and ongoing operation is an option — not something forced on you. The default is clean delivery: documentation, a tested suite, and software any Rails team can run. If you'd rather keep the person who built it on it, OctaneCare is the opt-in Operate & Run retainer — maintenance, monitoring, security updates, and incremental feature work, held to the same on-call standard Octane holds its own products to. It's month-to-month continuity, not a long lock-in.

One senior engineer — the founder, Evan Sparkman — with 15+ years shipping software and 13+ years on Rails specifically, and a career that runs from Senior Engineer to Web Architect to Head of Engineering at a fintech. There's no offshore hand-off and no junior bench: the person who scopes your project is the person who writes it and the person you talk to. It's the same standard applied to the products Octane builds and operates for itself.

The lowest-risk first step is The Diagnostic — a fixed-fee, time-boxed technical review that ends in a written deliverable you own: findings, risks, a recommended path, and a scoped estimate. For a new idea it's a feasibility and scoping read; for an existing app it's an audit of architecture, security, upgrade path, and tech debt. It de-risks the decision for both sides and lets everyone find out whether it's the right fit before committing to a large build. Or just tell Octane what you're building and you'll get a straight answer on how it would be approached.