Product
Every layer of a Laravel app, in one library
Properties make entities, entities and features make packages, and packages become applications. Each layer is reusable and versioned on its own.
Properties
Single reusable fields with everything a field needs: its type, validation rules, migration column and form control. Edit one, preview its form live, and publish it as a new version.
- Types, validation and column in one place
- Live form preview
- “Publish version N” tells you who uses it
Property bundles
Groups of properties that always appear together, like Contact Information or Money, added to an entity in one step.
- Bundles of related fields
- Versioned like properties
- Used across entities
Entities
Business objects such as Members, Orders or Elections, assembled from properties and bundles. The model and table names are derived for you.
- Built from properties and bundles
- Derived model and table names
- A detail panel for every entity
Features
Behaviour you attach to entities: CRUD management, authentication, search, soft deletes, notifications and approval workflows. Each one says its scope, what it generates and what it depends on.
- Scope and dependencies shown
- Generates controllers, routes and views
- Reused across packages
Packages
A set of entities and features with their relationships, models, controllers, views, roles and permissions, routes and API, database and tests.
- Entity relationship diagram
- View builder with a component palette
- Roles, permissions and routes
Relationships and views
Draw how entities relate, and lay out create and edit forms from a palette of components, with an inspector for each one.
- Has-one, has-many and many-to-many
- Form previews as you build
- An inspector for every component
Generate and deploy
A pre-deployment review lists errors that block the build and warnings worth reading. The build writes Laravel source, runs the generated tests and pushes to GitHub.
- Errors block, warnings are listed
- Generated test suite on every build
- Generating and pushing are separate steps
Applications and environments
Deployed packages become applications, each with its own configuration per environment.
- One application per package
- Configuration per environment
- Secrets referenced by name
Version history
Every library item keeps its published versions, who published them and when. Nothing is overwritten by a deployment.
- Immutable published versions
- Who published, and when
- “Update available” on packages that use it
Library assistant
Ask in plain language. The assistant suggests what your library is missing, drafts properties, bundles and entities, and adds them when you approve.
- Suggestions for gaps in your library
- Drafts from plain language
- Nothing added until you approve
In your language
The whole interface in English, French, Spanish and Arabic, with a right-to-left layout for Arabic.
- English, French, Spanish, Arabic
- Right-to-left layout
- Per-user language
