F.A.Q.

When will multi-user support be available?

Multi-user support is planned for release with the Cloud Enterprise subscriptions in 2025. This feature will enable users to manage multiple profiles, each with individual configurations and permissions, making it ideal for enterprise and collaborative environments.

What are the benefits of a Cloud Instance compared to a Self-Hosted setup?

Cloud Instances provide streamlined management with features such as automatic SSL certificates, dedicated support, regular updates, and automated backups. This setup is ideal for users seeking a secure, managed environment without the complexities of infrastructure management. In contrast, Self-Hosted setups offer greater control, catering to users with specific infrastructure requirements. However, they demand more user involvement for setup, configuration, and maintenance.

_{Self-hosted versions also support self-signed SSL certificates, just make sure to place them inside /DATA/SSLCerts and follow the guidelines under this section.}

How long are backups retained in the system?

Cloud Instances backups are retained in the system for 30 days before they are automatically deleted to free up space. We recommend recreating backups periodically if you need continuous data protection. We also plan to add an option for automated, recurring backups in the near future.

What is Shield Mode, and how does it protect my instance?

Shield Mode is a robust security feature in HomeDock OS, designed to safeguard against unauthorized access attempts. It actively monitors login behavior, triggering temporary lockouts when unusual login patterns or multiple failed attempts from various IP addresses occur within a short timeframe. This mode adds an additional layer of protection by automatically blocking suspicious activities, ensuring that legitimate users maintain safe access to the platform.

Note

We’re preparing to launch an MIT-licensed Python package, making our Shield Mode technology accessible to developers for broader security implementations to work along with Flask-Limiter.

Can I migrate my application configurations from one instance to another?

Yes, you can use the Export Config feature to download an exact configuration file (YAML) for an application, which can then be imported into another instance using the Replace Link feature. It’s important to note that only the application configurations are exported, not the data stored in /DATA/ApplicationName.

How easy is it to update HomeDock OS and my applications?

Installed applications can be updated directly from the administration panel. For Cloud Instances, HomeDock OS updates are automatic and deployed by us using infrastructure management tools. For applications, you can use the Update feature on each app, which will check for and install the latest version available, provided that port configurations and dependencies remain compatible.

What customization options does the Aero+ theme offer?

The Aero+ theme allows you to personalize the HomeDock OS appearance, including the option to upload custom wallpapers. This provides a visually appealing and tailored interface, perfect for users who want a modern and personalized experience.

What does enabling Development Mode entail?

Development Mode activates specific features for development and debugging, running HomeDock OS with Flask instead of production-ready servers like Hypercorn. This mode is not recommended for production environments and will be deprecated in the future, as it is currently intended only for internal testing and specific development adjustments.

_{Not recommended for production environments, it's a development option that regular users NEVER should use.}

Why PolyForm Strict Instead of MIT or AGPL?

HomeDock OS is currently source-visible under the PolyForm Strict license, not fully open source. This is a deliberate and temporary decision: the project is entirely self-funded, and as a SaaS-only platform, our software is our product. Unlike others, we don’t sell hardware, so releasing everything under a permissive license from day one would risk being outpaced or exploited by better-funded competitors before we have the chance to grow.

We believe in fair and reciprocal collaboration. Since we can’t yet offer the full freedoms of open source, we’re not accepting external contributions (PRs). It wouldn’t feel right to ask for help without being able to give back equally.

This is a protection phase, not a philosophy. Companies like Sentry and Plausible followed a similar model successfully. Once HomeDock OS becomes financially sustainable, we plan to transition to an OSI-approved license such as AGPLv3, allowing true open collaboration without compromising the future of the project.

We’d rather start protected and open up when we’re ready, than start open and be forced to shut down or restrict things later. It’s not strictly open source yet, but it will be.

_{In exchange, we're already releasing core parts under MIT such as vite-fusion, a core PIP package we had to develop to integrate Python/Flask with Vite.}

Why was Vanilla JS and CSS used instead of a modern frontend framework?

Although early internal prototypes used Vanilla JavaScript and CSS, HomeDock OS was publicly released directly with a modern frontend stack: Vue 3, TypeScript, and Tailwind CSS. This decision allowed us to provide a scalable, maintainable, and dynamic user experience from day one.

We are also actively working on multi-user support, which will be rolled out later this year alongside the Cloud Enterprise subscriptions.

This transition required us to develop vite-fusion , a key pip package for HomeDock OS, which facilitates the integration of Vite with Python/Flask. We have released vite-fusion under the MIT license, enabling seamless compatibility with modern frontend frameworks like React, Vue, Tailwind, and Svelte and so. This innovation ensures HomeDock OS remains at the forefront of modern web development while maintaining flexibility and stability.