rubys/roundhouse
Rails as a specification; the deployment target is a build flag
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
1 release in the last 90 days, the latest 42 days ago, with 34 contributors on GitHub.
Use Cases & Benefits
- Transpiles Ruby on Rails applications into standalone projects in multiple target languages using whole-program type inference without runtime dependencies.
- Enables high-performance, type-safe Rails app deployment by converting Rails code into native binaries or other language projects with verified conformance.
- Use for migrating legacy Rails apps to modern, compiled languages like Rust or Go to improve runtime performance and maintainability.
- Use for static analysis and type checking of Rails codebases without annotations, integrating with editors or CI pipelines for early error detection.
- Use for compiling Rails applications ahead-of-time into native executables with embedded databases for simplified deployment and faster startup.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Apache 2.0
Permissive: commercial use, modification and redistribution are allowed with attribution; includes an explicit patent grant from contributors.
Community files
- README: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
Rails as a specification; deployment is a build flag.
Roundhouse reads Ruby source — specifically, Rails applications — and produces standalone projects in other target languages. The deployment target (Rust or Swift binary, TypeScript bundle, Crystal or Go service, Elixir OTP app, Kotlin/JVM or C#/.NET service, Python project, browser bundle, or Spinel-compiled Ruby) becomes a compiler flag rather than a runtime choice.
A roundhouse is the circular hub in a rail yard where engines rotate and route onto different tracks. That's the pipeline shape: one Ruby source at the center, analyzed and dispatched to one of N target tracks.
For the case for doing this at all — the constraints that push successful Rails apps off CRuby, and the option value of preserving the choice — see WHY.md.
Three things, from one binary and one analysis. Each has a door in the user guide.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
+209 stars over 30 days across 9 snapshot days; best day +7 on Oct 4.
Forks
47+32
Open issues
199+103
Compared with peers in Backend
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| anthropics/skills | 187.8K | +2.9K | 15 | — |
| DuarteSantos8/openGym | 19.7K | +2.4K | 60 | 2 days ago |
| shiyu-coder/Kronos | 47.0K | +2.3K | 16 | — |
| NationalSecurityAgency/ghidra | 98.2K | +2.3K | 64 | 14 days ago |
| microsoft/VibeVoice | 56.0K | +1.1K | 29 | — |
| rubys/roundhouse | 517 | — | 53 | 42 days ago |
| Category median | 56.0K | +2.3K | 29 | — |
Discover Repositories
Search across tracked repositories by name or description