Build with Clinimatix Caravel
Expressive applications. Native .NET foundations. Learn the framework from your first route through data access, application services, and a repeatable development workflow on .NET 10 LTS.
26.1 Public Preview 1
26.1.0-rc1 is Caravel’s first public preview and first release candidate. These guides document its release snapshot, with installation guidance updated for NuGet availability. Public previews are for evaluation and integration ahead of stable release. Preview notes · Compatibility and adoption.
Start building
Install the public preview
Requires the .NET 10 SDK. Install Bosun from NuGet, then create and run an application:
dotnet tool install --global Clinimatix.Caravel.Bosun --version 26.1.0-rc1
caravel new MyApp
caravel serve --project MyAppAll twelve packages are available on nuget.org. Select Include prerelease in Visual Studio and pin 26.1.0-rc1. See the installation guide to add packages to an existing app. GitHub ZIPs and local feeds remain an alternative.
A quick look at routing
Define routes in an ordinary ASP.NET Core application. Caravel keeps native .NET tools within reach.
using Caravel.AspNetCore;
var builder = WebApplication.CreateBuilder(args);
builder.AddCaravel();
var app = builder.Build();
app.UseCaravel();
app.Routes(routes =>
routes.Get("/hello/{name}", (string name) => $"Hello, {name}!")
.Name("greeting"));
if (await app.ExportCaravelRoutesAsync(args)) return;
await app.RunAsync();Explore the framework
- Clarion data access — models, queries, transactions and soft deletes on EF Core.
- Authentication — opt-in registration, email confirmation, password recovery, authenticator-app MFA and recovery codes; separate guides cover OIDC, bearer tokens and Windows sign-in.
- Queues and workers — durable jobs, renewable leases, retries, recovery and transactional outbox dispatch.
- Transactional mail — SMTP, templates, attachments, capture and queued delivery.
- Mail and SMS notifications — replaceable channels, independent retries and a Twilio adapter.
- Bosun tooling — models, migrations and seeders from the command line.
- Backend walkthrough — see authentication and background processing together.
Choose your documentation
The RC1 docs stay pinned to the published release. The separate development docs track a reviewed source snapshot and are labeled unreleased, even when their source currently matches RC1. Use documentation versions or the version selector to switch.
Review the RC1 changelog and roadmap for current limits and future work. Account screens, passkeys, calendar scheduling, cloud storage and AI/MCP remain planned. Mail/SMS delivery needs verification with your chosen provider; SMS delivery is not SMS MFA.
