Introducing Orchestry: Manage Teams with Hostinger
Summary
This announcement showcases the launch of Orchestry, a private workspace for managing teams and tasks, built within the Hostinger ecosystem. By leveraging Hostinger AI Builder and a custom Node/Express API on a Hostinger VPS, the project demonstrates how to build scalable organizational tools. It highlights the importance of scope discipline and technical implementation, offering valuable insights for developers looking to build and deploy their own management solutions.
What I shipped:
A working MVP of Orchestry, a private workspace for organizations to manage people, teams, and tasks.
Core features:
Organization workspaces with invitations, three fixed roles (admin/manager/member) with restricted notes and per-field visibility, tasks with Kanban boards and comments, in-app notifications, activity history, data export, and a workspace deletion. Built primarily in Hostinger AI Builder, with a custom Node/Express + PostgreSQL API on a Hostinger VPS backing part of the data layer.
What I learned:
Scope discipline was the hardest and most valuable part. The idea kept wanting to grow into a full HR suite and cutting that back to a focused core was what made it buildable in the time I had.
Building the VPS-side API from scratch (auth, routes, permissions, deployment) taught me a lot.
AI Builder credits run out faster once you're iterating on permission logic, worth budgeting more conservatively for that than for the visual/content side.
What I'd do next:
Get a few real organizations or NGOs to try it and stress-test whether the permissions model solves a problem they actually have. Before trusting it with anything beyond demo data, I'd want to properly harden the VPS API (it's currently running with some testing-era configuration I haven't gone back to lock down) and get a real security review of the permission enforcement.
Also I would work on the pricing and branding more then move to adding new features like a daily mood checker for the employees/team members and add custom roles and more sets of permissions and isolation between teams.
Discord sent us an expired image link.
The most fun thing for me was configuring the VPS (nothing beats a Linux machine with only a terminal and SSH connection xD). Getting the API to work was frustrating but that's how it goes lol
Other than that, I had a big issue coming up with the idea at first since I couldn't pick one project idea. I ended up settling on this one because of my previous experiences as head of IT & head of HR departments in an NGO i worked in. This tool wouldve helped me and my team a lot and I still believe it can help others too.
One thing that the Agent highlighted was the competition:
Services like trello for example already exist so I had to think of a way to be more unique that's why i decided to implement the role and permission system and keeping the pricing affordable for everyone and free for NGOs (after verification ofc)
Review done !
Discord sent us an expired image link.
