TruffleRuby ships two distributions and makes you choose at install time
A high performance implementation of the Ruby programming language, built on GraalVM.
At a glance
- What is it?
- TruffleRuby arrives as a Native or a JVM distribution with different names in every Ruby manager, different startup and peak behaviour, and a dependency list that decides whether RubyGems loads at all.
- Who is it for?
- TruffleRuby is a real option for a long running Ruby service that can afford warmup and a C toolchain, and its pass rate of around 98 percent of ruby/spec is the strongest compatibility claim any alternative Ruby implementation makes.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Ruby, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- truffleruby/truffleruby3,228 ★ · +3
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| truffleruby/truffleruby | 3.2k | 3.2k |
3 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Two distributions and two names in every Ruby manager
TruffleRuby ships as two separate downloads, and the choice made at install time decides what that installation is for the rest of its life. The Native Standalone carries only the Native configuration. The JVM Standalone carries only the JVM configuration, and that build is the one carrying support for other languages such as Java, JavaScript, Python and WebAssembly. Since each distribution holds exactly one configuration, the name encodes the choice, and a Ruby manager shows two entries for the same project. The Native names take a version suffix:
$ rbenv install truffleruby-VERSION
$ ruby-build -d truffleruby-VERSION ~/.rubies
$ asdf install ruby truffleruby-VERSION
$ mise install ruby@truffleruby-VERSION
$ ruby-install truffleruby
$ rvm install truffleruby # or truffleruby-headThe JVM names insert a segment in the middle instead:
$ rbenv install truffleruby+graalvm-VERSION
$ ruby-build -d truffleruby+graalvm-VERSION ~/.rubies
$ asdf install ruby truffleruby+graalvm-VERSION
$ mise install ruby@truffleruby-VERSION
$ ruby-install truffleruby-graalvmTwo details in those lines are easy to miss. ruby-build is called with a -d flag and given ~/.rubies as its target directory on both distributions, and ruby-install takes no version argument at all, so on a machine with several Rubies it resolves to whichever one it finds. VERSION is a placeholder, and the stated recommendation is to try the dev builds by writing dev in its place, since those contain the latest fixes and improvements. Continuous integration goes through the same naming scheme, where the setup-ruby action accepts all four variants:
- uses: ruby/setup-ruby@v1
with:
ruby-version: truffleruby # or truffleruby-head or truffleruby+graalvm or truffleruby+graalvm-headOnce one of them is installed, gem and bundle install gems as they do on any other Ruby.
Reading which configuration you actually ended up with
Native is the default and the JVM build is selected with the --jvm flag, so one machine can hold both without either being wrong, and nothing in the version string tells you which one a given install is. The documented trade-off between them is short enough to set out whole. Native starts in about the same time as MRI startup and reaches peak performance faster. JVM starts slower and takes longer to get there, but its peak performance, counting garbage collection, is the better of the two, and interop with a Java host just works instead of needing a reflection configuration. That last row is the reason to reach for JVM: the Native build can talk to Java hosts, but only once reflection configuration is in place, so a deployment built around that interop can break on the configuration you did not pick. Settling which one you have is a one-liner either way. Run ruby --version on the command line, or read the value of RUBY_DESCRIPTION, or ask TruffleRuby.native? from Ruby code. Any of the three answers it without inferring anything from the install path or the manager you used.
Container images cover only the Native distribution
The Native Standalone has release images and nightly images published under the project's container packages. The JVM Standalone has none. For that build the documented route is to download it and take inspiration from the Native Standalone Dockerfiles, which leaves the container recipe for the JVM configuration for you to assemble rather than shipped for you. A team that standardised on images for one distribution cannot assume the other is a tag away, and mixing the two recipes is exactly what the pointer to the Native Dockerfile invites. Note also what a nightly image gives you: a moving target, so a deployment that pins versions has to decide which of the two tag families it trusts. Container images are not the only route either, since manual installation has its own document, and the manager commands from the previous section need no container at all. Whichever route you take, gem and bundle are expected to work afterwards, so the gem ecosystem is not the part that changes between distributions.
The performance claim is paired with a warmup bill
TruffleRuby states that it is by far the fastest Ruby implementation on the yjit-bench suite, which includes railsbench, and it links a 2022 benchmarking article that covers CRuby, MJIT, YJIT, JRuby and TruffleRuby side by side. The same section attaches the cost: reaching that performance needs a fair amount of warmup, as other advanced JIT compilers do, and there is a separate guide for reporting performance problems when you find one. Put that beside the runtime table and the shape of the trade becomes concrete. Native startup is about as fast as MRI, so short lived work is not where a difference shows up, and the peak numbers only arrive after the warmup. A resident process such as a request server or a worker stays inside that window long enough to collect it. A job that starts, does one small piece of work and exits does not. The compatibility figure quoted in the same section, around 98 percent of ruby/spec passing, is the other half of the status picture: more of the suite passes here than on any other alternative Ruby implementation, and it is still not 100 percent compatible with MRI 4.0 yet.
RubyGems will not load without a C toolchain and two libraries
The dependency list is short and each item carries weight. make, gcc and g++ are what you need for building C and C++ extensions. CA certificates are what the openssl C extension needs. zlib is what the zlib C extension needs. Without those three, many libraries stop working, and the one named explicitly is RubyGems itself, so a missing compiler toolchain shows up as a package manager that will not start rather than as a failure in the extension you were trying to install. The diagnostic is best effort: TruffleRuby tries to print a readable message when a dependency is missing but cannot promise it will. Two requirements sit outside that list. A UTF-8 locale has to be in place if it is not already, and building from source follows a separate contributor workflow rather than the manager commands above. The other side of the same coin is that many C extensions work out of the box, database drivers among them, and thread-safe native extensions run in parallel with Ruby code because there is no global interpreter lock.
The tested platform table lags the release tags
The systems listed as actively tested are Oracle Linux 7, 8 and 9, Ubuntu 18.04, 20.04 and 22.04, Fedora 37 and 38, Debian 10, 11 and 12, and macOS 11 Big Sur. Architectures are narrower still: AMD64 is supported on Linux, and AArch64 is supported on Linux and on macOS. That pairing has a direct consequence for desktop machines, since an AArch64 Mac is inside the stated support while an Intel Mac is not, because AMD64 support is stated for Linux only. The releases carrying those numbers are current. graal-40.0.0, which is TruffleRuby 40.0.0, was published on 2026-09-17, following graal-34.0.1 on 2026-04-26 and graal-34.0.0 on 2026-04-12, and the last commit to the default branch is dated 2026-09-26. So the code being current sits next to a platform table naming distribution releases from several years back. That is the mismatch to check first when a base image you want to deploy on is not in the list, since the answer there is a question for the project rather than something the table settles.
Version numbers track CRuby while Graal leads the tag
A TruffleRuby version AB.C.D is meant to be compatible with CRuby A.B, so 34.0.0 targets CRuby 3.4 and 40.0.0 targets CRuby 4.0. That mapping explains something that otherwise looks contradictory: the release line has moved well past 34, while the compatibility statement still says TruffleRuby is not 100 percent compatible with MRI 4.0 yet. Two further versioning facts matter when you pin something. TruffleRuby releases on its own schedule, driven by features and important bug fixes, and does not follow the GraalVM release schedule, so a GraalVM version number says nothing about when a matching TruffleRuby will appear. And the last release that used GraalVM and Truffle versioning together was 25.0.0, which is where the older tag style stops. The Graal version is not a free choice either: the Truffle version is fixed and is a dependency of the dev.truffleruby:truffleruby Maven artifact, so it cannot be chosen by whoever builds against it. The compatibility table that would set out the pairing stops partway through explaining that constraint.
The licence field and the licence file disagree
Two things in the repository speak about licensing and they do not line up. The licence recorded for the project reads NOASSERTION rather than naming terms, while the root holds LICENCE.md and, next to it, 3rd_party_licenses.txt for vendored components. The file listing gives the names and not the contents, so which terms attach to which file cannot be settled from the names alone, and anyone using this as a dependency has to read both files or ask. Nothing else in the tree chooses between them. The rest of the root does show how the project is built and checked: a .ruby-version file, RuboCop and Reek configurations aimed at its own Ruby sources, mx.truffleruby/ for the GraalVM side of the build, a SECURITY.md, an AGENTS.md, and the bench/, spec/, test/, src/, lib/, exe/, bin/ and doc/ directories around them.
Editorial conclusion
TruffleRuby is a real option for a long running Ruby service that can afford warmup and a C toolchain, and its pass rate of around 98 percent of ruby/spec is the strongest compatibility claim any alternative Ruby implementation makes. Before adopting it, check three things: which of the two distributions your managers and images can actually give you, whether your base system and CPU appear in the tested list at all, and which CRuby version your application expects, because the release line and MRI 4.0 compatibility do not line up yet. If your workload is a pile of short lived scripts, or your laptop is an Intel Mac, the honest answer from these files is that the documented advantages are the ones you will not reach.
Frequently asked questions
Is JRuby faster than Ruby, according to TruffleRuby's own numbers?
No such comparison is published in these files. What is written is a claim about TruffleRuby being by far the fastest Ruby implementation on the yjit-bench suite, a link to a 2022 benchmarking article covering CRuby, MJIT, YJIT, JRuby and TruffleRuby, and the note that reaching peak performance needs a fair amount of warmup.
Is Ruby on Rails still being used, and does TruffleRuby run it?
The status section states that TruffleRuby runs Rails and is compatible with many gems, including C extensions. railsbench is part of yjit-bench, the suite named as the place where TruffleRuby is by far the fastest Ruby implementation.
Is Ruby a dead language, and is TruffleRuby still moving?
These files make no adoption claim about Ruby as a language. TruffleRuby's own activity shows in its releases: graal-40.0.0 on 2026-09-17 after graal-34.0.1 on 2026-04-26, with the last commit to the default branch dated 2026-09-26.
Is Ruby on Rails a coding language that TruffleRuby compiles?
Nothing in TruffleRuby classifies Rails either way. What the files state is that TruffleRuby runs Rails, that TruffleRuby version AB.C.D aims to be compatible with CRuby A.B, and that TruffleRuby is not 100 percent compatible with MRI 4.0 yet.
Which TruffleRuby Docker image should a deployment use?
Release and nightly images exist for the Native Standalone only. For the JVM Standalone there are no images yet, and the documented route is to download it and take inspiration from the Native Standalone Dockerfiles in the repository.
What licence is TruffleRuby released under?
The recorded licence field reads NOASSERTION while the repository root holds LICENCE.md and 3rd_party_licenses.txt. The listing does not say which terms cover which file, so the pairing has to be read from both files rather than assumed.
Official sources
Where developers are discussing it
Posts on Hacker News, dev.to and Lobsters that link to this repository, found by our scan of those communities. 1 in the last 30 days; newest first.
- TruffleRuby – High performance implementation of RubyHacker News · Oct 22, 2026 · 1 points · 0 comments
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/truffleruby-truffleruby)Star history chart for your README
[](https://hysenlabs.com/projects/truffleruby-truffleruby)Was this useful?