Modern frontends for ASP.NET Core apps
An Inertia.js v3 adapter for .NET 10. Keep your routes, auth and validation in C#. Build the UI in React, Vue or Svelte. Inertia.Net connects the two, so you skip the API layer and the client-side router.
Use the frontend you already know. The server code is the same for all three.
React
@inertiajs/react
Vue
@inertiajs/vue3
Svelte
@inertiajs/svelte
The JavaScript ecosystem, without the extra work
A separate SPA usually means an API, a client router, auth on both sides and duplicated validation. Inertia.Net removes that layer so you can spend the time on the product.
No API layer to build
Your endpoints return a page name and its props. There are no DTO endpoints, fetch hooks or client-side router to keep in sync with the server.
Interfaces your users will like
Write the UI in React, Vue or Svelte with their component libraries and tooling. Navigation stays fast, and server-side rendering makes the first load quick.
Easier to maintain
Routing, auth and validation stay in C#. Shared TypeScript types come from your .NET contracts, so a renamed property shows up as a compile error.
Faster with AI agents
One repo, one request flow and a small set of conventions. Agents can add a page end to end, and the docs ship an agent guide and llms.txt.
How it works
- 1
Return a page from C#
An endpoint, controller action or FastEndpoint calls Render with a component name and props.
- 2
Render it with your framework
Inertia resolves the component in your frontend and passes the props in. The first visit is plain HTML.
- 3
Navigate without full reloads
Links and forms make Inertia requests. The server answers with the next page and the client swaps it in.
Ready for production
The adapter covers the whole Inertia v3 protocol and the parts a real app needs around it.
Working with an AI agent?
Give your coding agent the conventions it needs to add pages, props and forms correctly. The agent guide has a ready-made AGENTS.md section, and the whole documentation is available as plain text.