ruby.ci

What It Is

RubyCI is a cloud CI platform built specifically for Ruby on Rails teams, created by the Kolosek team. Its core positioning is not general-purpose pipeline orchestration, but letting Rails projects “connect a repository and run”: it automatically detects the Ruby version, database, test framework, and asset pipeline, reducing the maintenance overhead of YAML, Docker, and pipeline definitions. The site emphasizes early access, batch onboarding, and claims the first green build can be completed in about 5 minutes.

Core Features

Functionally, RubyCI is designed around the Rails delivery workflow. For testing, it has built-in support for RSpec and Minitest, with parallel execution, intelligent test splitting, and per-file duration and failure reports. For quality and security, it integrates SimpleCov, RubyCritic, Bundler Audit, and Brakeman, covering test coverage, complexity/duplicate code, Gem vulnerabilities, and Rails security issues. It also supports Jest for frontend testing in Rails applications. On the infrastructure side, the site says each build runs in a fresh container that is destroyed after the build, data is encrypted at rest and in transit, and 99.9% uptime is provided.

Pricing and Value

RubyCI uses fixed monthly pricing rather than usage-based billing. The Free plan includes 1 shared worker and limited builds; Starter has a promotional price of $49/month with 2 workers; Team is $149/month with 5 workers; Business is $349/month with 10 workers. All paid plans include unlimited builds, no per-seat charges, and no overage fees, with 2 months free on annual billing. For Rails teams with frequent builds and multiple team members, this model is easier to budget for than CI services priced by minutes or seats.

Pros and Cons

The advantages are clear positioning, a strong Rails-native experience, and a comprehensive set of built-in tools, which can significantly reduce CI configuration and maintenance work. Fixed pricing is also attractive for teams that do not want build volume fluctuations to affect costs. The downside is that the available information is still limited: there is no visible API/SDK, self-hosting option, deployment region information, compliance certification, or detailed documentation. The product is also clearly best suited to Ruby/Rails; if a team has a complex multilingual monorepo or highly customized pipeline requirements, a general-purpose CI platform may still be more flexible.

Who It’s For and Access from China

RubyCI is suitable for Ruby/Rails startups, small and mid-sized product teams, Rails consulting firms, and teams currently using GitHub Actions, CircleCI, or Jenkins but struggling with slow builds, complex configuration, and fluctuating bills. The site does not provide information about access from mainland China, so actual network connectivity and payment options need to be verified through a trial. Alternatives include GitHub Actions, CircleCI, Jenkins, and Travis CI. If localization or self-hosting is required, options such as Jenkins should be evaluated first.