From separate tools to shared infrastructure
Project Win uses custom software and self-hosted tools for company operations. In July, its company HQ and DreamCatcher dashboard moved from shared infrastructure to a dedicated Project Win server.
The server gives those applications a home the team can access while individual laptops are closed. Running applications still requires monitoring, updates and someone responsible for recovery.
What is running there
| Need | Application | Purpose |
|---|---|---|
| Coordination | Custom HQ and dashboard | Shared views of company work. |
| Social scheduling | Postiz | A self-hosted scheduling application. |
| Shared records | Baserow | A database interface for the team. |
| Learning | Learnhouse | A self-hosted course platform. |
Keep useful managed services
Project Win continues to use managed Supabase services for its product. The server supports company applications and scheduled database backups, without requiring every part of the product to be self-hosted.
The September 23 server log confirmed a successful database dump. File storage needs separate protection, and backup creation alone does not prove a successful restore.
The useful result
The company has a place to deploy custom tools and selected existing applications, with shared access for the team. The ongoing work is keeping that infrastructure useful and recoverable.
No net savings figure is claimed. Hosting, service charges and the time needed to operate the server belong in the comparison.
Start with the workflow.
The $495 Software & Workflow Assessment looks at one recurring problem, compares up to three researched options, and gives you a written recommendation with costs and maintenance responsibilities. Implementation is quoted separately.