If you’ve been watching the Dart backend ecosystem, you’ve probably come across Serverpod.
Type-safe endpoints. Code generation. A Dart-native ORM. Auth. Real-time. Built specifically to pair with Flutter. The Serverpod team has shipped something that makes building a full-stack Dart application genuinely possible and they’ve done it with a level of care that shows in every release.
I’ve been building with it in production. And the experience of working with the core has been good. But the longer I used it, the more clearly I could see one gap.
The gap: no visual layer for designing your backend
Serverpod developers currently have no visual way to design and architect their backend.
Every schema change means running the generator and then re-reading the output to reorient because there’s no diagram that updates automatically. Every endpoint test means writing curl or maintaining a Postman collection in parallel. Every time you want to understand your architecture, you open files.
Compare this to the Flutter app side: Flutter DevTools gives you a widget inspector, a performance overlay, a network monitor. The app is legible. You can see it. You can reason about it visually.
The Serverpod backend doesn’t have that yet. It’s not a criticism; it’s just where a growing framework is in its journey. The core is exceptional. The visual tooling layer is still being built.
I wanted to help build it.
What I built: Dartform
Dartform is a visual IDE companion for Serverpod developers. It gives you the ability to design, architect, and navigate your Dart backend visually without digging through generated code to understand what you built.
It’s a native macOS application. It reads your existing Serverpod project; no configuration, no backend changes, no new dependencies and gives you:
An auto-generated ER diagram built from your schema files. Every model, every relationship, every field type rendered as a navigable diagram that updates as your schema evolves. Your backend architecture, visible at a glance.
An endpoint browser with request testing built in. Browse all your Serverpod endpoints in one view. Test requests without leaving the tool; no Postman, no curl scripts, no external collection to maintain.
A model and relationship viewer. Navigate your backend the way you navigate your Flutter app by looking at it, not by reading files about it.
What Dartform isn’t
Dartform isn't here to compete with Serverpod, it's built to complement it. Think of it as a productivity layer that sits on top of your backend workflow, making the day-to-day faster and more visual. Serverpod is the first integration, but the vision is broader; more Dart backend solutions are coming.
Who it’s for
Dartform is built for Flutter developers who run Serverpod in production on macOS currently, and who have felt the absence of visual tooling without quite having a name for it.
If you’ve ever re-read generated files to understand a schema you designed yourself, Dartform is for you.
A note on the ecosystem
To the Serverpod team, thank you for building something worth building around. Dartform exists because your framework does. Keep going.
Serverpod deserves a rich visual tooling ecosystem. This article, and this tool, are my contribution to building one.
Dartform is available now at dartform.dev, distributed as a desktop tool.
Feature requests and feedback live at https://dartform.dev/#community . If you’re using Serverpod, I’d genuinely love to hear what’s still missing.
Top comments (0)