Welcome to the LaraSchema blog
A short note on what this blog is for, who it's for, and what you can expect to find here.
Welcome. This is the LaraSchema blog — a place for notes on Laravel database design, migrations, Eloquent, and the ecosystem that surrounds them.
What you'll find here
This blog isn't a content factory. It's a working notebook for problems we hit while building LaraSchema and patterns we find useful while designing Laravel schemas. Expect posts like:
- Walkthroughs of common schema design problems (many-to-many with extra columns, polymorphic relations, soft-deletes done right)
- Comparisons with other tools — what LaravelSD did well, what's missing from the current generation of Laravel ERD tools
- Release notes when we ship something interesting
- Opinions on Eloquent patterns that show up in real projects
Why a blog at all?
LaraSchema is free to use. We don't have ads, a sales team, or a freemium tier to upsell. The way a tool like this gets discovered is by writing things that other Laravel developers find useful — and trusting that some of those readers will give the tool a try.
If that's you: start a project and tell us what's missing. Every suggestion shapes what we build next.
Subscribe — or don't
There's no newsletter signup popup on this page. If you want to follow along, bookmark /blog. We'll add a feed when the posts add up to enough to subscribe to.
Thanks for reading.
Try LaraSchema yourself.
Drag-and-drop database design for Laravel. Free to use, no credit card required.
Start designingMore articles
Need this actually built?
Exporting migrations is the easy part. If you would rather an experienced Laravel team wrote the application around your schema, tell them what you are building.
Talk to a Laravel team