Continued Development
Over the last stretch, we have been pushing multiple projects in the same direction: fewer disconnected tools, more ownership, and a platform stack we actually control end to end.
That is the thread running through all of this work. We are moving away from stitched systems and into software that fits how we actually operate day to day.
HH Panel
HH Panel has been the biggest part of that move.
We came from a split model where WHMCS handled billing and the panel handled most VM operations. It worked, but it always felt temporary. As we grew, it became obvious we needed to own the full flow ourselves.
That is what this phase has been about: deeper billing integration, cleaner customer journeys, stronger self-serve ordering, smoother reinstall workflows, better app lifecycle handling, stronger ISO upload and delivery, tighter security, better console and service workflows, and BGP/self-serve capabilities as part of the same product.
The important part is not the bullet list. It is the outcome. Less reliance on external systems, lower overhead, faster iteration, and more room to keep package pricing sensible for customers.
VigilPing
VigilPing has had a major UX and workflow push as well.
The status experience is much cleaner now: clearer uptime visuals, better monitor cards, stronger branding, improved monitor detail pages, incidents where they should be, and more reliable custom-domain loading.
This is the kind of work that looks small on paper until you use it. Status products are trust products. If the UI feels unstable or messy, confidence drops immediately. If it feels clear and intentional, that trust compounds.
This push was about exactly that: stronger product identity and a better day-to-day experience for teams relying on it.
ACloud
ACloud has moved forward in quieter ways, but useful ones.
Recent work focused on making the site better for publishing and easier to read: cleaner blog layout, wider reading widths, syntax highlighting, copy-code controls, clearer content cards, better docs structure, improved paste moderation and SEO handling, production caching improvements, and general UX polish.
Not flashy work, but high-leverage work. The platform is easier to navigate and better suited to the kind of technical content we want to publish.
Nodalo
Nodalo has also been progressing steadily.
The recent focus has been on product quality, not feature bloat: monorepo publication, harder EL install paths, and continued inventory/UI improvements.
That matches where Nodalo needs to be. If it is going to be a serious bare-metal orchestration platform, reliability and cleanliness have to stay ahead of raw expansion.
The Bigger Picture
Across all four projects, the pattern is the same.
- more control over customer experience
- cleaner admin workflows
- less dependency on third-party systems
- lower operating overhead
- more room to improve pricing
- a stronger long-term foundation for growth
That is the real reason for this push. Not feature count. Not vanity metrics. Building a platform that feels like ours, top to bottom.
Recent Verified Stats
- VigilPing: 11 commits · 57 files changed · 3,252 insertions · 798 deletions · +2,454 net lines
- HH Panel: latest verified major commit touched 51 files · 5,549 insertions · 1,899 deletions
- ACloud: recent work focused on blog/UI/SEO polish
- Nodalo: recent work focused on monorepo publishing, install hardening, and UI/inventory improvements