Ruby on Rails development
Ruby on Rails development at a fixed price: a first version of a new application, one feature, a fix, or monthly maintenance.
We also run a Rails application of our own. Japan Voyage is built on Ruby on Rails, runs on Rails main, the development branch of the next Rails, and runs in production on Ruby master, the nightly build of the next Ruby. When a new Rails or Ruby version changes something, we usually meet it in our own production first, before it reaches a client's application.
What we build
- New Rails applications: a first version you can launch, then further work one fixed-price piece at a time
- Features in existing applications: payments, search, real-time chat, notifications, admin tools
- Hotwire front ends instead of a separate JavaScript application, so one team can own the whole product
- Mobile apps with Hotwire Native, sharing screens with the web application
- Multilingual sites, with proper hreflang, locale routing and translation workflows
- Performance work: finding and fixing what makes pages or background jobs slow
Existing Rails applications
Much Rails development is work on an application that already exists, often one that another team wrote. We start by reading the code and running the test suite, and we tell you what we found before we quote anything large.
If the application is several Rails or Ruby versions behind, we usually suggest an upgrade roadmap first, because features are cheaper to add on a current version. If you are not sure what state the code is in, or you want an outside opinion on another vendor's proposal, start with a code audit or second opinion.
Phoenix and Elixir
We also build applications with Phoenix and Elixir, and we have worked on real-time, WebSocket-heavy systems with Phoenix Channels as well as ActionCable. If a project would be better served by Phoenix than by Rails, we will tell you.
How we work
We work in your repository and through your review process. You see every change as a pull request, with tests, before it is merged. We write down decisions that the next developer will need, and we stay with Rails conventions unless there is a reason not to, because conventions are what make an application cheap to hand over.
We are two engineers. You talk to the people who write the code, not to an account manager.
How a project runs
- You send a few lines through the contact form about the application and what you need. We reply within two business days, in English or Japanese.
- We agree the scope and a fixed price before we start. Prices are in US dollars, and invoices in yen are fine.
- The work arrives as pull requests with tests, in your repository, and you merge it when you are happy with it.
- After launch, the monthly maintenance plan covers security updates and small changes, and gives you someone who knows the code.
Proof
We build and run our own product on the same stack: Japan Voyage, a Rails application that serves four sites in five languages from one codebase, with iOS and Android apps built on Hotwire Native. It runs in production on Rails main and Ruby master.
Sampo Kuokkanen heads the Japan office of Evil Martians, contributes to Ruby, JRuby and Spinel, and has spoken at Kaigi on Rails, RubyWorld Conference, RubyConf Taiwan and COSCUP.
Pricing
Prices in US dollars, before tax. A price marked "from" is the minimum; we agree a fixed price before we start, and invoices in yen are fine.
Feature or fix
from $1,000
fixed quote
One well-defined piece of work: a feature, a performance problem, an integration with a payment provider or an external API.
Small application
from $5,000
fixed quote
A first version of a new application, sized to what you need to launch, with a fixed price agreed before we start.
Maintenance
from $500
per month
Security updates, small fixes and changes, and someone who knows the code when something breaks.
Frequently Asked Questions
- Do you build new applications or only work on existing ones?
- Both. For a new application we start with the smallest version that is useful to real users and build from there.
- Which stack do you use?
- Current Rails with Hotwire (Turbo and Stimulus), Tailwind CSS, PostgreSQL or SQLite, and Kamal for deployment. For mobile we use Hotwire Native, which wraps the Rails views in iOS and Android apps.
- Can you work with our in-house team?
- Yes. Most of our work is in a client's repository, through their pull request review, on their issue tracker. We are happy to pair with your developers.
- Do you work in Japanese?
- Yes. Specifications, meetings and documentation can be in Japanese or English, and we can work with a Japanese team and an overseas team on the same project.
- Can you take over a Rails application another team built?
- Yes. We read the code and run the tests first, and tell you what we found before quoting larger work. If the application is on an old Rails or Ruby version, an upgrade roadmap is often the first step.
- Do you also work with Phoenix and Elixir?
- Yes. We build Phoenix/Elixir applications as well as Rails ones, and we have worked on real-time, WebSocket-heavy systems with both Phoenix Channels and ActionCable.
- How do we get started?
- Send a few lines about your application and what you need through the contact form, or email sampo@sampo.ltd. We reply within two business days with next steps and a rough estimate, and we agree a fixed price before any work starts.
Tell us about your project
Send a few lines about your application and what you need. We reply within two business days, in English or Japanese, with next steps and a rough estimate.
Other services
Rails and Ruby upgrades
Move an old Rails application to current Rails and Ruby step by step, without a rewrite and without stopping feature work. We start with a fixed-price roadmap.
Upgrade roadmap: $1,500
Code audit and second opinion
An outside review of your Rails codebase, or of a proposal you have been given, written up in plain language so you can decide what to do next.
Second opinion: $500