Build Modern SPAs Without Writing APIs.
Inertia.js bridges Laravel and Vue/React with server-side routing and client-side navigation. Get the best of both worlds: no API endpoints, no token management, no complexity—just build.
This Website Uses Inertia.js
kamlogic.com is built with Laravel 11 + Inertia.js + Vue 3. Zero API endpoints. Server-side rendering for SEO. TypeScript throughout. We practice what we preach.
How Inertia.js Works
No magic, just smart protocol design. Here's the request flow from click to render.
User clicks a link
Inertia intercepts the click
XHR request to Laravel
Sent with X-Inertia header
Controller returns data
No Blade view, just JSON props
Vue component renders
Client-side update, no page reload
Example: Laravel Controller
// Laravel Controller
public function index()
{
return Inertia::render('Dashboard/Index', [
'users' => User::all(),
'stats' => $this->getStats()
]);
}
// That's it! No API routes, no serializers, no token management.What You Get with Inertia.js
Build full-stack applications with half the complexity of traditional SPA + API architecture.
Inertia Architecture Fundamentals
Server-side routing with client-side navigation. The best of both worlds.
- Server-side routing (no API routes needed)
- Client-side navigation (SPA feel)
- Automatic CSRF protection
- Shared data and props between backend/frontend
- SSR ready for SEO optimization
When to Use Inertia vs API
Strategic decisions for architecture that scales.
- Internal tools & dashboards → Inertia (simpler)
- Mobile apps or third-party integrations → API
- Hybrid approaches for flexibility
- No authentication complexity (sessions work)
- Faster development without API layer
Developer Experience Benefits
Build full-stack apps with half the complexity.
- No API documentation needed
- Direct controller-to-component data flow
- Shared validation rules (backend & frontend)
- No token refresh logic needed
- Hot reload with Vite for instant feedback
When to Use Inertia.js (and When Not To)
Inertia shines for specific use cases. We'll tell you honestly if it's the right choice.
Internal Admin Dashboards
Perfect Fit
No SEO needed, no mobile app planned, no third-party integrations. Inertia removes all API complexity while keeping SPA feel.
Customer Portals (Web Only)
Excellent Choice
If you're building web-only and don't need external API access, Inertia is simpler than React SPA + Laravel API.
Mobile App + Web Dashboard
Build Laravel API Instead
Inertia won't work for mobile apps. You need a proper REST/GraphQL API that both web and mobile can consume.
Complex Real-Time Features
Use with Caution
Inertia works with WebSockets (Laravel Echo), but complex real-time features may be easier with a dedicated API layer.
Inertia.js in Practice
One real implementation (this website) and common scenarios where Inertia simplifies full-stack development.
This Website (kamlogic.com) — Real Implementation
Challenge
Build marketing site and interactive pages without duplicate code or API complexity
Solution
Inertia.js with SSR for SEO, Vue 3 components, Laravel 11 backend, TypeScript throughout
Result
Single codebase, 99 Lighthouse score, zero API endpoints needed, easy to maintain
Property Management Dashboard Scenario
Challenge
Real estate agents need fast CRUD operations, property listings, tenant management without page refreshes
Our Approach
Inertia + Vue with optimistic UI updates, Laravel backend for validation and business logic
Expected Outcome
Instant navigation between property records, 50-60% faster development vs building separate API layer
School Administration System Scenario
Challenge
Complex permissions for teachers/admins/parents, student records, grade management, attendance tracking
Our Approach
Inertia with shared Laravel policies for authorization, server-side validation, role-based UI components
Expected Outcome
Secure role-based access control, single source of truth for permissions, maintainable authorization logic
Frequently Asked Questions
Common questions about Inertia.js, when to use it, and how it compares to alternatives.
What exactly is Inertia.js?
Inertia is a protocol/library that lets you build SPAs using server-side routing. Instead of building a Laravel API + separate Vue app, you write normal Laravel controllers that return Vue components instead of Blade views. No API layer needed. It's the glue between your Laravel backend and Vue/React frontend.
Can I use Inertia with React instead of Vue?
Yes! Inertia works with Vue, React, and Svelte. We prefer Vue with Inertia since they share similar philosophies, but React works fine if your team is more familiar with it. The Inertia protocol is framework-agnostic on the frontend.
Does Inertia work for SEO (marketing sites)?
With server-side rendering (SSR), yes. Inertia SSR prerenders your Vue components on the server, so search engines see fully rendered HTML. Without SSR, Inertia behaves like a SPA (poor SEO). For marketing sites, we always enable SSR. For internal dashboards, it's not needed.
What happens if I need a mobile app later?
You'll need to add a Laravel API. Options: (1) Add API routes alongside Inertia (hybrid), (2) Migrate Inertia pages to consume the new API, or (3) Keep Inertia for web, build separate API for mobile. We help you plan ahead to minimize future migration work if mobile is on your roadmap.
Is Inertia production-ready? Who uses it?
Absolutely. Inertia is used by thousands of production apps, including this website (kamlogic.com). Created by Jonathan Reinink (former Laravel employee), it's battle-tested and actively maintained. The Laravel community widely adopts it for internal tools and dashboards.
Ready to Simplify Your Architecture?
If you're building internal tools, dashboards, or web-only applications—Inertia.js eliminates the complexity of API layers while keeping the SPA experience. Let's discuss if it's the right fit for your project.