Notploy is open-source infrastructure software, Apache-2.0 licensed. Whether you deploy with it, report issues, write docs or ship code — there is a clear way to participate.
Stars, contributors and license are visible to anyone. Here is where you can check the project for yourself.
GitHub Stars
Notploy is developed in the open on GitHub. Follow the repository to track releases, issues and roadmap work.
+
Community Contributors
Built with the community: contributors have helped with code, documentation, integrations and translations.
+
License
Notploy is open source under the Apache-2.0 license. Audit it, self-host it and modify it.
Apache-2.0
Self-hosted
Run Notploy on your servers, your network and your database — or use Notploy Cloud if you would rather not manage the control plane.
Your servers
Not every contribution is code. These are the paths that keep the project moving.
Found something broken? Open a GitHub issue with reproduction steps. Security vulnerabilities follow a private disclosure process instead.
GitHub Discussions and Discord are where questions, ideas and deployment stories are shared — with maintainers and other operators.
Pick up an issue, fix a bug or ship a feature. The codebase is Apache-2.0 and contributions are reviewed in the open.
Docs are a contribution surface too: clearer guides, missing examples and corrected steps help every new user.
Add blueprints to the templates gallery so others can deploy complex applications in one click.
Help present Notploy to non-English speaking communities and make the project accessible worldwide.
Larger changes start as a discussion: describe the problem, the proposal and the trade-offs before code is written.
Vote on priorities, comment on proposals and help decide what the project builds next.
The license and the development process are part of the product. Both are meant to be read.
Enterprise features are available under a commercial license maintained by Sky Genesis Enterprise — the core platform stays open.
Source code, issues, discussions and roadmap decisions happen in public repositories — anyone can follow along.
The core platform is free to use, modify and redistribute, for individuals and organizations alike.
Reviews, design discussions and trade-offs are visible, so the project's direction is never a black box.
Three honest entry points, whether you are deploying for the first time or writing your first patch.
Read the documentation, deploy a first application, then tell how it went. Feedback from new users is the most valuable there is.
Look for good-first-issue labels on GitHub, or bring a problem you actually have — both are valid entry points.
Ask in Discussions or Discord. Chances are someone already hit what you are hitting.
Deploy your first application on infrastructure you own — self-hosted with Notploy Self, or managed with Notploy Cloud.