API Gateways / API Management systems --

1. Fusion https://www.fusio-project.org/

2. Improve documentation for Kong self-host -- i've spent hours debugging (and still doing it) why it doesn't want to talk to PSQL https://railway.com/deploy/Addl8t

3. Unkey https://github.com/unkeyed/unkey

It's lightweight, yet meets the basic needs of an API gateway:

https://railway.com/deploy/IR4lVv (a bit of self-promotion)

I'm working on adding more features but I don't have much time after work. Feel free to create an issue with features you would like to have and I will prioritize them.

Postgres GUI: https://mathesar.org/

Segment clone: https://jitsu.com/

Bookmarking: https://karakeep.app/

100% wish Chatterbox (open source alternative to Eleven Labs text to speech) was a template. I tried to set it up myself but couldn't figure it out.

https://github.com/resemble-ai/chatterbox

This requires a GPU. Railway is unable to provision GPUs atm

PostgresSQL 17 . The source image seems to be there, but the SSL template still uses 16.

azuracast

Maybe this is too much, but hey, just a thought:

One idea that could perhaps be implemented is to support different versions in templates.

This way, for example, we could have different versions of Postgres: version 16 of the template could correspond to version 16 of Postgres, and version 17 to version 17, and so on. This way, the same template could support multiple versions of the underlying tech.

This would also allow community-developed templates to have a specific version, and users could deploy the one they want. For example, if I have a template with two services, an API and a DB in version 1.0, and then I add another service with a website for the API management part... users can't deploy that new service alone; the update button only appears when the services already deployed changes. It would be great if version 2.0 includes a new service, and the template could be updated to version 2.0 and this new service deployed.

Finally, if the service is from a GitHub repo, It would be great to be able to select the branch to deploy, so we can have beta versions on one branch and more stable versions on another branch.

No Code Architects Toolkit https://github.com/stephengpope/no-code-architects-toolkit

Wekan https://github.com/wekan/wekan

Mathesar and Karakeep done

hola.

algun template de evolution.api?

Simple configurable prometheus, without a need to have in the github repo, just a template and it is ready to go

A Supabase template with a 100% successful deploy rate. Currently Railway does not have one, which is unexpected for such a popular database. I don't deploy anything that's not at 100%.

Same goes for ClickHouse and Metabase.

A scheduler with a UI like Cronicle (although I'd prefer something even simpler to use).

And then, Vanna.ai and its competitors like MindsDB.

And finally, why not a version of AnythingLLM with models deployable internally instead of via API? AnythingLLM is not yet perfect but way better for no-code audience than Ollama + OpenWebUI.

All of these tools are no or low code. You guys are all in the same low-code boat, you might as well start lending hand to each other.

For now you can change the image tag to 17, nuke the db, then restart, you'll get v17

https://railway.com/deploy/postgres-17 This is what I created by cloning the official Railway template but updated to image 17.