Weave Code
Runway Laravel Package
doublethreedigital/runway
Runway lets you use Eloquent models as first-class resources in Statamic, giving editors a familiar control panel for creating, editing, and listing database records without building custom addons. It bridges Laravel models with Statamic’s content workflow.
Eloquently manage your database models in Statamic.
Frequently asked questions about Runway
- What is Runway for Statamic and when should I use it?
- Runway is a Statamic addon that turns Laravel Eloquent models into first-class Statamic resources, so database records show up in the Control Panel with blueprints, listings, search, sorting and front-end routing. It is a strong fit when your relational database is already the system of record for things like products, venues or people, and you want editors to manage that data without building a custom Control Panel from scratch. It is a poor fit if your content is author-owned flat files with no database backing, or if you plan to move delivery to a headless CMS.
- How do I install Runway in a Laravel app with Statamic?
- Install it with Composer as doublethreedigital/runway, then publish its config file and register your resource classes in that config. Standard practice is to start read-only with a single low-risk resource, confirm the Control Panel and front-end behaviour, and then expand to additional models. Check the install and upgrade docs for the exact publish and registration commands for the version you are pinning.
- Does Runway duplicate my database records into Statamic's flat-file content?
- No. Runway reads from your existing database tables through Eloquent, which is the main reason to use it when you do not want domain data copied into Statamic's flat-file content layer. Your models, relationships and schema remain the source of truth, and Statamic supplies the editing interface, routing and content API around them. Content edited in the Control Panel is written back to the database rather than to Markdown or YAML files.
- Which Statamic, Laravel and PHP versions does Runway v9 support?
- Runway v9 is a major-version line, so its Statamic, Laravel and PHP constraints are declared in its composer.json and covered in the v9 upgrade guide. Verify those constraints against your current stack before committing, because moving from an earlier Runway major is a migration project rather than a patch upgrade. Pin the version you validate and read the upgrade guide in full before bumping it in production.
- How do I turn an Eloquent model into a Statamic resource with Runway?
- You create a resource class that points at your Eloquent model, register it in the Runway config, and attach a blueprint that defines the fields editors see in the Control Panel. Once registered, the resource appears in the Control Panel for browsing and editing and can be used in your Antlers or Blade templates. Existing relationships and custom resource settings can be carried over, so you do not need to reshape your models to fit Statamic.
- Can editors create, edit, search and reorder Runway records in the Control Panel?
- Yes. Runway provides Control Panel listings with search and sorting, plus the familiar create and edit flows driven by your blueprint. Version 9.7.0 added orderable resources, which give you drag-and-drop ordering against an order or sort column, closing a long-standing parity gap with Statamic collections. Ordering generally requires a schema change, and you should confirm the expected column naming and scoping conventions in the docs before migrating.
- How does front-end routing work for Runway resources?
- Runway supports flexible route configuration that maps front-end URIs directly to your Eloquent models, so model records can be resolved and rendered like any other Statamic content. That keeps delivery inside the Laravel runtime, which is convenient for a monolith but ties your front end to Laravel if you later consider a headless approach. Route patterns are configured per resource, so you can keep existing URL structures intact during a brownfield integration.
- How does Runway interact with Statamic static caching?
- Runway records served through Statamic routes can be captured by static caching, and version 9.7.0 added the ability to disable static cache warming for Runway URIs. That option decouples URI warm-up from deploy and rebuild cycles, which matters on larger sites, but confirm in the config and upgrade guide whether the new default preserves your current behaviour. If you enable orderable resources, make sure reordering invalidates warmed URIs and any CDN or queued purge, or the Control Panel and front end will disagree.
- Does Runway expose resources through GraphQL and REST as well as templates?
- Yes. Runway resources are usable in Antlers and Blade as well as Statamic's GraphQL and REST APIs, which is what makes it attractive for API-driven front ends backed by a Laravel database. Whether newer capabilities such as ordering and nested JSON title formats appear in the API schema or are Control Panel only should be verified in the docs for your pinned version. Test the specific fields you rely on before exposing them to external consumers.
- Who maintains Runway, and what are the alternatives?
- Runway is maintained by Double Three Digital as a single-maintainer addon with a small contributor base, which is acceptable for a commercial dependency but belongs in your risk register. If you need a formal support contract for production incidents, confirm whether a commercial path exists before relying on it for critical editorial workflows. The practical fallback is querying Eloquent directly and building custom Control Panel screens, so keep that option documented in case the addon stalls or a future major upgrade becomes costly.
Weaver
How can I help you explore Laravel packages today?