When building Serversinc, I’ve found that development naturally splits into two parts: about 70% backend and API work, and 30% dashboard and frontend work. Because of this imbalance, many features are released through the public API first, before they appear on the dashboard.
This isn’t just a side effect of development; it's a deliberate strategy to build a better, more reliable service for Serversinc's customers.
Why I’m Building API-First
There are a few reasons why I choose to launch features on the API before adding them to the dashboard:
1. The dashboard is built with Livewire, and it's starting to show its limits
The current dashboard is powered by Livewire, which made it fast to build the initial version. But as Serversinc grows, I’m pushing up against the edges of what Livewire can handle easily. Some features that would be straightforward in Vue 3 are much harder to implement in the current setup.
By building and testing each feature through the API first, I’m setting up a smoother path for transitioning to Vue when the time is right.
2. APIs are easier and faster to test
Before I commit to building out a user interface, I want to know that the feature actually works. That means validating the logic behind server actions, container commands, or resource handling through the API.
This helps me avoid wasting time on interfaces that don’t quite fit the functionality. Once a feature is proven to work reliably at the API level, I can design the frontend with confidence that it has a solid foundation.
3. APIs unlock more than just the dashboard
Building reliable APIs has benefits beyond the web interface. It also opens the door to:
-
A CLI tool for managing servers directly from the terminal
-
Integrations with third-party platforms like CI/CD services or orchestration tools
-
Faster iteration when adding or improving features
This flexibility is part of how I’m designing Serversinc to grow beyond just being a dashboard and become a full platform for managing apps and infrastructure.
What This Means for You
You’ll notice that many new features show up in the API before they’re visible in the dashboard. This might seem like a delay, but it’s part of a strategy that allows me to move faster, test more thoroughly, and ensure that what ends up in the UI is actually useful and stable.
If you want to explore new features early or integrate Serversinc with your own tools, check out the API documentation here:
https://dash.serversinc.io/docs
New endpoints and capabilities are added regularly, and they’ll always be available in the API before anywhere else.
Check out the features page to see what's available on the Dashboard or API