Put your Rails upgrades on autopilot
Our team of specialized agents built on our upgrade methodology iterates until your own test suite is green, and sends you tiny, reviewable pull requests only when they're ready for human review. Your team keeps shipping the product roadmap.
Sure, you could use your own tokens, but why waste so many tokens when you could just use our optimized AI solution?
Plans run from $497 to $897 per month. No long-term commitment.
The upgrade always loses the prioritization fight
Every quarter it's the same conversation. The Rails upgrade is on the list, everyone agrees it is a priority but then an urgent commitment or a launch pushes it to next quarter. Again.
- Your Rails version stops receiving security patches, and the CVEs don't stop.
- Gems drop support for your version one by one, and every workaround becomes load-bearing.
- Each Rails release you skip makes the eventual jump harder and more expensive.
- Compliance reviews and enterprise customers start asking uncomfortable questions.
- The roadmap pays the bills. But while it wins every sprint, technical debt keeps growing quietly.
- We've spent more than a decade upgrading Rails apps, and the pattern is always the same: the cost of the upgrade was never the problem. The cost of displacing the roadmap was.
What if the upgrade didn't need a sprint slot at all?
Imagine the upgrade running in the background, every day, without borrowing a single engineer to do hands-on work. Imagine your senior leaders reviewing and approving tiny pull requests that take you one step closer to the latest versions of Ruby and Rails.
It plans the path
An agent that reads your Gemfile.lock, plans the safest path from your Rails version to the latest stable versions of Ruby and Rails by addressing deprecation warnings and changing your source code to avoid breaking changes.
It runs your suite
It runs your test suite after every change, and keeps iterating until everything is green. Not green on a demo app. Green on your CI, your jobs, your suite.
Then it opens pull requests
Then, and only then, pull requests show up in your repo: a steady stream of tiny ones, plus one big PR per version jump, the one that bumps Ruby or Rails. Each carries a description that explains every change and a passing build. Your team reviews and merges them like any other PR. That's the whole interruption.
That's AI-native Rails Maintenance. Upgrade projects stop being a quarter you have to put your product roadmap on hold and it turns into a set of tiny, reviewable PRs that reduce the risk of big-bang deployments to production.
From install to your first pull request in about a week
Four steps, and only the last one asks anything of your team.
Install the GitHub App.
Read-only at first. You pick exactly which repositories it can see.
Our agent starts the upgrade process using your CI workflow.
The agent runs on your own CI runners, not ours. If your suite is green there, you're eligible, and that green run becomes the baseline every change is measured against.
The agent iterates.
Built on the same methodology behind 100+ upgrades, the agent detects every breaking change and deprecation for your specific version jump, applies fixes, and runs your full CI after each round. You see none of the trial and error. That's the point.
The pull requests land in your repo.
Tiny PRs most of the time, and one big PR per version jump: the commit that bumps Ruby or Rails. Each one comes with a full write-up of what changed and why, and your CI already passing. Your team reviews the PR and merges it into the main branch.
Your first pull request lands within a week of install.
An agent you can let near your codebase
Every guardrail below is enforced by your tooling, not by a promise.
Your tests are the judge.
A PR ships only when your own CI is green, with the same jobs your branch protection requires. Not our tests. Yours.
It can't touch your CI config.
Our GitHub App doesn't request the permission GitHub requires to edit workflow files, so the agent cannot change the jobs that judge its work. This is enforced by GitHub itself, not by a promise.
No quiet test deletions.
Green with fewer tests than your baseline doesn't count as green. Every skipped or removed test is listed in its own section of the PR description for your reviewers.
Invisible until it's ready.
All iteration runs on your own CI runners, on branches the agent works in, so your main branch never sees the trial and error. You see one thing: the finished PR.
Humans stay in the loop.
Your team reviews every PR, and we recommend you keep branch protection requiring your own review on merge.
Nothing reaches production without your approval.
The agent only ever opens pull requests. Merging, deploying and releasing stay exactly where they are today: with your team and your pipeline.
Beta pricing, locked in for waitlist members
Plans run from $497 to $897 per month depending on how much agent work your app needs each month, measured in credits. No long-term commitment. Waitlist members keep their beta price after launch.
Best for one app making steady progress.
- 10M Credits are FastRuby.io's own unit, not a specific provider's tokens, because we're provider-agnostic. per month
- Email support
- Month to month, cancel anytime
Best for one app at a faster pace.
- 30M Credits are FastRuby.io's own unit, not a specific provider's tokens, because we're provider-agnostic. per month
- Slack support
- Everything in Starter
Best for a large app or an aggressive timeline.
- 70M Credits are FastRuby.io's own unit, not a specific provider's tokens, because we're provider-agnostic. per month
- Slack support
- Everything in Standard
Not sure which plan fits? Talk to us about your Rails application and we'll help you pick a starting tier.
Two ways to get maintained. Both use AI.
The difference is who's driving.
AI-native Rails Maintenance · $497 to $897/mo
- An AI agent does the work, and your team reviews every PR.
- Best fit: Rails 6.1+, Ruby 3.0+, green suite on GitHub Actions.
- Tiny upgrade PRs, plus one big PR per version jump, each opened only when your CI is green.
- Your involvement: review and merge.
- Month to month.
Monthly Rails Maintenance · from $1,950/mo
- Senior engineers do the work, paired with AI agents.
- Best fit: complex apps, older versions, rescue work, strategy.
- 4 to 8 senior-engineer PRs per month, plus quarterly reporting.
- Your involvement: review and merge, plus a monthly huddle.
- Month to month.
Plenty of teams will move between these plans in both directions. Start AI-native and escalate to senior engineers when your app needs rescue work or architectural decisions, or start with Monthly Rails Maintenance and hand the well-trodden work to the agent once your app is current.
AI-native Rails Maintenance is in private beta
We're onboarding a small number of teams while we harden the service, and we review every application before we say yes. That's deliberate: we'd rather tell you "not yet" in week one than waste your money.
- Join the waitlist and we'll reach out with your locked beta price.
Join the waitlist
Tell us where your application is today. We come back with your locked beta price.
We'll only use this to evaluate your app's eligibility and to contact you about the beta. We don't sell or share your data.
Frequently asked questions
Monthly Rails Maintenance puts senior engineers on your app directly, and they handle anything: rescue work, old versions, architectural decisions. AI-native Rails Maintenance is our agent doing the well-trodden part of that work (version bumps, deprecations, breaking changes) at a lower price, and you only see it once your CI is green. Plenty of teams will graduate from one to the other in both directions.
A GitHub App install on the repos you choose, CI on GitHub Actions, a test suite that passes today, and credentials for any private gem sources your build needs.
For the beta, yes. Join the waitlist anyway and tell us what you run; it directly shapes what we support next.
The beta targets apps on Rails 6.1+ and Ruby 3.0+. Older than that usually means rescue work, which is what our human-led plans are for, and we'll tell you that honestly when we review your application.
Credits measure how much work the AI agent does on your app each month. A small app close to current uses fewer; a large app several versions behind uses more. Upgrades are hard to predict, so we don't promise an exact number up front. Talk to us about your application and we'll suggest a starting tier; you can change tiers month to month.
It stops cleanly instead of thrashing, and we look at where it stalled. Sometimes it's a missing credential or an unmaintained gem blocking the path; sometimes it's a sign your app needs the human service. Either way you hear from a person, not a status page.
It only ever opens them. And because we recommend branch protection requiring your team's review, the merge stays fully in your hands regardless of what any tool can do.
Your code stays in your GitHub account and runs on your own CI runners. The agent only sees the repositories you choose. We've handled client codebases this way since 2012; happy to walk your security team through the GitHub App's permission list, including what we deliberately don't request.
Stop deferring the upgrade. Your roadmap doesn't have to pay for it anymore.
Join the waitlist and we'll come back with your locked beta price.