Introducing Ryft 0.3 / Developer preview ↗A clearer language
A clearer language
for the backend.
Explicit types. First-class apps. Native executables.
Build services in a language that makes your
backend's boundaries part of the code.
>
ryft init hello-worldYour next project starts here. Windows x64 preview · Open source · MIT licensed
app hello {
base "/api";
budget connections 32;
get "/hello/{name}" -> Json {
return json({
"message": "Hello, " + param("name")
});
}
}>
ryft build main.rz -o hello.exe✓Native executable. Ready to run..exe↳ Your app is the program. The runtime supplies the server.
FROM SOURCE TO NATIVEHow it works ↗
your-service.rz→Ryft type checker→Rust / Cargo→your-service.exe ↗DESIGNED AROUND THE SERVICELess scaffolding.
Less scaffolding.
More of your application.
Routes, types and storage live together.
The boundaries stay explicit.
Types you can follow.
Model your domain with structs and enums. Handle expected failures with Result, Option and exhaustive matching.
Explore the language ↗Backends, in the language.
Declare apps, routes, environment capabilities and storage ownership. Connect to SQLite or MongoDB from native code.
Build a service ↗A familiar place to work.
Stay in VS Code with diagnostics, navigation, references, formatting and checked rename. Bring your own editor via LSP.
Set up your editor ↗THE NEXT FEW STEPSFrom a blank file
From a blank file
to your first service.
A practical guide, one concept at a time.
Explore all documentation →