Introduction

InertiaX adds server-driven Tables to an existing Laravel, React, and Inertia application. You point a Table at an Eloquent model, choose the behavior your users need, and render the named Inertia prop on the page.

Laravel keeps ownership of authorization and database work. React gets a complete Table UI, while InertiaX coordinates search, filters, sorting, pagination, URL state, and fresh results.

Before you begin

This guide starts with an application that already has:

• Laravel 12 or 13;
• React 19;
• a matched Inertia 2 or Inertia 3 server/client pair.

If you are creating a new application, start with Laravel’s official React starter kit, confirm the starter application works, then return to the InertiaX installation.

You do not need to reinstall React or Inertia when adding InertiaX.

The first useful Table

The shortest path uses your existing User model:

return Inertia::render('Users/Index', [
    InertiaX::table('users')
        ->data(User::class)
        ->autoColumns()
        ->filterableColumns()
        ->autoFilters(),
]);

Then render the prop with the normal Inertia integration:

<InertiaX prop="users" />

The installation guide mounts InertiaXProvider once above the Inertia application, so page components only render their named Table props. That is the normal customer path. Your first Table walks through the complete controller, page, and route.

What InertiaX owns

• Table definitions and Eloquent or Collection execution in Laravel.
• A complete React Table with strong defaults.
• Search, filters, sorting, pagination, selection, and visibility state.
• Inertia partial reloads, request cancellation, latest-result safety, and URL state.

Your application still owns routes, authorization, models, domain queries, page layout, and any business operation outside Table presentation.

Where to go next

• Early access — request access and connect the temporary private registries.
• Installation — install InertiaX and configure the application provider.
• Your first Table — reach a working model-backed Table.
• Columns — replace inference where your domain needs explicit presentation.
• Filters and Clauses — customize filtering after the automatic baseline.
• Recipes — copy focused patterns once the basics are working.