Akaganite · Managed Rust toolchain for licensed console developers
Skip to content
Request access
rust on playstation 5 and xbox
Another platform for your Rust project.
A managed Rust toolchain for licensed console<br>developers. One command sets it up and consoles<br>become another cargo target. We are onboarding teams<br>to the alpha by invitation.
Request access
How it works
~/project
Replay demo
Use the Replay button below the terminal to replay<br>the demo. Keyboard users may also press Y.
just another rustup target
Three commands. No patched compilers in tree.
The workflow stays inside cargo and rustup. No bespoke<br>build system, no local fork of rustc.
step 01
cargo login --registry akaganite
Authenticate with the mirror.
Opens your browser, authenticates against the<br>Akaganite mirror, and stores a refresh token in<br>cargo credentials.
step 02
rustup target add ps5-dev
Install the target.
Adds the PS5 or Xbox target like any other Rust<br>target. Standard library, cross-compiled and<br>verified on real hardware.
step 03
cargo build --target ps5-dev
Build your project.
Build, test, and link with the cargo commands<br>your team already uses. The console target is<br>just another entry in the matrix.
From the engineer's perspective, consoles become another<br>target. No patched compilers in tree, no separate build<br>pipeline.
library coverage
Three tiers of crate coverage.
Everything we ship runs on real consoles before it<br>reaches your build. The tiers describe how each crate<br>gets there.
tier 1<br>verified
Hand-adapted, hardware-tested.
Crates adapted by hand and served from our cargo<br>mirror. End-to-end verified on real console<br>hardware on every toolchain release.
libc
ring
rustls
mimalloc
tokio
serde
rayon
hyper
tier 2<br>auto-adapted
Patterns we have automated.
Crates whose porting patterns we have automated.<br>Built and tested end-to-end on real consoles in<br>our mirror's CI before they reach you.
✓ verified<br>end-to-end in our mirror CI
on request
Anything else.
If your project needs a crate we have not yet<br>ported, we port it for you.
When several teams need the same crate, or one<br>team needs production-grade support for it, we<br>promote it to verified as part of the<br>engagement. No per-crate surcharge.
request via the form below
release commitment
Monthly releases. Stable and nightly. Both verified on<br>hardware.
Each monthly release ships two toolchains in parallel.<br>Both are pinned and both pass our PS5 and Xbox devkit<br>suite before publication.
stable channel
Pinned to upstream Rust stable.
Each monthly drop is pinned to the current<br>upstream stable. Verified on real console<br>hardware before release.
nightly channel
Pinned to a 30-day-old upstream nightly.
Nightly is a first-class deliverable. Teams that<br>rely on unstable features for performance work<br>get the same hardware verification and support<br>window as stable users.
12 months
Standard support window on every monthly<br>release, both channels, security backports<br>included.
24 months
Long-support window on one release per quarter,<br>both channels.
integration
White-glove on our side, cargo on yours.
Your team treats consoles as another cargo target.<br>We handle adaptation, mirror operations, toolchain<br>updates, and porting on request. The operational<br>surface is the same one your engineers already know.
production track record
Built by engineers who have shipped Rust on<br>consoles.
We shipped production Rust subsystems in retail PS5<br>and Xbox titles, covering networking, payments, and<br>real-time audio. The work was production code on<br>production schedules, not research.
That experience is what Akaganite is built on: real<br>build systems, real engine boundaries, real devkit<br>debugging loops, and the submission schedules that<br>come with shipping on console.
frequently asked
Things teams ask us.
What engines does Akaganite support?
We do not currently provide engine-specific<br>support. The toolchain works for any Rust<br>project including engine-integrated subsystems.<br>If you want full coverage for a particular<br>engine (Bevy, Fyrox, or a proprietary engine),<br>bring it up in your request and we will scope<br>it.
How do crates get promoted between tiers?
Customer demand. If multiple teams need the same<br>crate, or a single team needs production-grade<br>support for one, we move it from on-request to<br>verified as part of the engagement. Pricing is<br>per-seat. No per-crate surcharge.
Where can we ship Akaganite-built code today?
Xbox is fully supported end to end: build, ship,<br>done. The other console we support is<br>dev-preview only for now. That vendor recently<br>tightened its rules around which compilers are<br>approved for shipping titles, and Akaganite is<br>not on the current list. You can build, run, and<br>profile on devkits there today, just not ship a<br>retail title. If your studio would like to<br>collaborate on opening this up, reach out.
What does the NDA cover?
Source access to the toolchain, the cargo mirror<br>credentials, and any console-vendor-derived<br>materials. Your...