Show HN: Swiftwave – Simple Lightweight Open Source PaaS

[TanmoySarkar]

Hi HN! I am Tanmoy & today I am releasing stable V2 of Swiftwave.

SwiftWave is a self-hosted, lightweight PaaS solution for easily deploying and managing your applications on any server . It's an open-source alternative to Heroku, Netlify, and Render.

You can install swiftwave in bare metal, Raspberry Pi, in any VPS(Hetzner, DigitalOcean, Linode, AWS, GCP etc.). Swiftwave and its dependencies are compatible with AMD64, ARM64 and ARMv7 architectures and compatible with Debian/Ubuntu/Raspbian OS/Fedora/CentOS/AlmaLinux/RockyLinux.

Checkout https://swiftwave.org/ for more details.

If you like the project, consider to give this project a star in Github: https://github.com/swiftwave-org/swiftwave

[josephcsible]

This is not open source, because this is in the license:

> Additional Information:

> If there is any conflict, the rules in this section are more important than the usual rules of the Apache License.

> - Without a special written agreement, you can't modify the paid features of SwiftWave.

> - Without a special written agreement, you can't share or sell another paid version of SwiftWave.

> - Also, if you change the free features of SwiftWave and want to redistribute, you have to share those changes for free and need to keep the changes open source.

[TanmoySarkar]

Moved to Apache 2.0 from the modified Apache 2.0 and removed the point of conflicts. Check the discussion for more details - https://github.com/orgs/swiftwave-org/discussions/680

The license was initially written after checking various existing solutions like this (you can check caprover's license)

We are changing it because,

- I just came to know, Apache doesn't allow the modification in the license. Although there are many popular projects which is using that. So, I thought initially, It may be allowed.

- I don't want to move to GPL/AGPL for a small restriction which is only on the paid features of Swiftwave (which even doesn't exist, I don't know if someday any paid features will come or not).

- If there will be any paid feature in future, that can be in a different variant than the open source one. (Same way like docker or HAProxy) So we can keep Swiftwave as Open Source in Apache 2.0 and keep all the features available for free.

[josephcsible]

That's perfect now. Thank you!

[TanmoySarkar]

Thanks !

[CoolCold]

Mind highlight differences/advantages over Dokku?

> An open source PAAS alternative to Heroku. > Dokku helps you build and manage the lifecycle of applications from building to scaling.

Good luck with your project!

[TanmoySarkar]

Dokku is a great and matured tool for managing lifecycle of applications. But that's heavily on CLI. They have some web UI also but in Commercial version.

My focus is to build a PAAS which will have a great GUI to interact. So that anyone with little less knowledge of linux can even deploy apps with swiftwave.

Whenever we deploy in Heroku, Render or Railway to deploy app, we don't need to think much about underlying stuffs. I want to create similar kind of experience with Swiftwave.

Swiftwave handles many stuff other than lifecycle of app. It handles

> Application Deployment from git/image registry/uploaded code + Application Monitoring + Web SSH console for application + Webhook to trigger re-deployment of apps

> It uses docker swarm, so easily deploy apps across cluster also. Swiftwave completely support all the stuffs to work across cluster.

> Managed Ingress (HAProxy for TCP/HTTP/HTTPS, Custom built udp proxy)

> Domain + SSL Management (With Let's encrypt integration with auto-renewal support)

> Persistent Volume Management (Check size, Backup [local+s3], Restore of volume)

> Server Management ( Easy Onboarding + Server Monitoring + Web SSH Console for server )

> It has also a integrated app-store to install app at single click.

You may check the website to learn about all the features - https://swiftwave.org/

[CoolCold]

Thank you!

Sounds like something I should find project to play around with Swiftwave