Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Database wise, depending on your expected load I'd say stick with sqlite. This is especially nice if you combine it with litestream.io which streams any changes to the database to object storage every second by default. It doesn't allow you to run multiple instances of the same database but it can get you really far when you scale vertically. After that you'll probably know better what you require from your stack.
If you don't really need specific kubernetes features then I'd say don't. Just use as service that takes a container image as input and runs it for you. Google'se Cloud run does this as does fly.io (awesome stuff btw). This still leaves you room to just move to kubernetes or nomad or what not because your artifact is just a container which can run anywhere.