Coming to Go from Laravel
People come to Go for the deployment story: one static binary, small memory, no runtime to install, trivial containers. They stay for the type system. What catches them out is how much Laravel was doing that they had stopped noticing.
This page maps each part of Laravel to its nearest Go equivalent and is honest about the four that have no good answer. It is not an argument that Go is better. For a content-shaped application with a small team, Laravel is frequently the right tool and moving would be a mistake.
Star counts and activity dates checked against each project's source on 13 November 2026. Numbers move; the reasoning does not.
The map
| Laravel | Nearest in Go | How close |
|---|---|---|
| Eloquent | GORM | Close |
| Query builder | sqlc or Bun | Different, often better |
| Artisan | cobra, or the framework’s CLI | Close |
| Migrations | golang-migrate, Atlas, GORM AutoMigrate | Close |
| Blade | templ or html/template | Close |
| Queues and Horizon | asynq | Close |
| Scheduler | robfig/cron, asynq scheduler | Close |
| Validation | go-playground/validator | Close |
| Mail and notifications | Resend, SES, gomail | Assembly required |
| Storage | AWS SDK, MinIO client | Assembly required |
| Breeze and Jetstream | Nothing standard | Gap |
| Filament | Nothing standard | Gap |
| Policies and Gates | Nothing standard | Gap |
| Tinker | Nothing standard | Gap |
What transfers well
Eloquent to GORM
GORM is the closest thing Go has to Eloquent and the transition is genuinely comfortable: struct tags instead of fillable arrays, Preload instead of with, hooks with familiar names. The differences that catch people are that there is no model boot magic and no global scopes in the Laravel sense, so a soft-delete or a tenant filter is something you compose rather than something that happens to you.
Artisan to a CLI of your own
cobra is what everything in Go uses, and writing myapp migrate or myapp seed takes minutes. What you lose is the hundred commands Artisan gives you for free; what you gain is that your commands compile.
Queues to asynq
asynq is Redis-backed, has retries, dead letters, scheduling and a web dashboard. It is the closest thing to Horizon in any language outside PHP, and it is good.
Blade to templ
If you are staying server-rendered, templ gives you components that are checked at compile time, which Blade cannot do. Paired with HTMX it covers most of what Livewire is used for.
The four gaps
1. Starter authentication
php artisan breeze:install gives you registration, login, password reset, email verification and the screens for all of it. Go has excellent libraries for the pieces, and no standard assembly of them. Every Go team writes this, and most write it slightly wrong the first time, usually around token rotation or timing differences between a wrong password and an unknown account.
2. The admin panel
Filament is the single hardest thing to leave. A resource class produces a table with search, filters, sorting, bulk actions and a form, in an afternoon. The Go options are older, thinner or a different product entirely. Compared in full here.
3. Policies and gates
Laravel's authorisation is a convention everyone follows: $user->can('update', $post), with a policy class per model. Go has Casbin, which is powerful and is not that. Most teams end up with permission checks spread through handlers, which is exactly where authorisation bugs live.
4. Tinker
A REPL against your live models, with your relationships loaded. Go is compiled and has no real equivalent, and the usual answer is to write a small command and run it, which is slower in the moment and leaves something reviewable behind.
Is it worth moving?
Move for: deployment simplicity, a compiled type system, concurrency as a first-class feature, memory that does not scale with request volume, and the hosting bill that follows from those.
Do not move for: raw speed in a request that spends its time waiting for Postgres. Laravel with Octane and a tuned database is not the bottleneck people assume.
Think carefully if: your application is mostly forms over a database and the team is small. That is exactly Laravel's strongest ground, and the four gaps above are precisely the work you would be taking on.
Where Grit fits
Grit was built against this list. The four gaps are its entire reason for existing, and the influence is deliberate: the resource definitions are modelled on Filament, and the scaffolded authentication is Breeze's scope.
- Breeze: registration, login, password reset, email verification, two-factor, sessions you can revoke, and the screens, scaffolded.
- Filament: a generated React admin per resource, with a table and a form built from the same field definitions.
- Policies: roles and permissions, plus declarative row rules that filter a query rather than checking after the fact.
- Artisan: a CLI that generates resources, runs migrations, seeds and deploys.
It uses GORM, so Eloquent habits transfer, and asynq, so Horizon habits do too. The honest caveat: the admin is React, not Blade or Livewire, so there is a frontend build in your life that Laravel did not require.
Frequently asked questions
- Is there a Laravel for Go?
Not with Laravel's completeness. Buffalo is the closest in design and has slowed; Beego is the largest and is a different idea of a framework; Grit covers the starter-auth and admin gaps with a React frontend. All of them are compared here.
- What is the Go equivalent of Eloquent?
GORM, and it is a close one. For teams who prefer writing SQL, sqlc generates typed Go from your queries, which has no Laravel analogue and is better than the query builder for complex reads.
- What is the Go equivalent of Filament?
There is no standard one. GoAdmin renders server-side admin screens, PocketBase bundles a dashboard with its backend, and Grit generates a React admin from your Go models. The comparison is here.
- Is Go faster than Laravel?
For CPU-bound work and high concurrency, substantially, and it uses far less memory per request. For a request that spends its time waiting on Postgres, the difference is much smaller than the benchmarks suggest. Deployment and memory are the stronger arguments.
- Can I keep writing server-rendered HTML in Go?
Yes. templ gives you typed components compiled to Go, and with HTMX it covers most of what Livewire is used for. You give up the React ecosystem and gain a single deployment artefact with no JavaScript build.
