I also requested these 7 months back here https://station.railway.com/community/what-templates-do-you-wish-existed-865e6f36#88bs

Hey there! We've found the following might help you get unblocked faster:

• 📚 Railway vs. Fly

• 📚 Deploy a Lovable App on Railway

• 📚 Using Variables

• 🧵 templateDeployV2 failing for AnythingLLM (HNSCS1) template – request for assistance

If you find the answer from one of these, please let us know by solving the thread!

@cocashen I'm not sure we're on the same page here.
The ask here is to create a Railway template that allows one-click self-host/self-deploy for Unkey.dev - http://github.com/unkeyed/unkey/

An example Railway template for Typesense - https://github.com/railwayapp-templates/typesense

On a side note, I've found Flexprice.io to be a very strong API Billing management solution. I'm trying out their cloud offering, but would be good to have their Railway template as well!

@cocashen - can you move the railway template to a new github repo?
Also, to confirm, have you gotten a chance to try deploying it on Railway, and tested some of the Unkey's functionalities yourself?

I've got ~6 hours this Saturday lined up to work on getting this up as an actual template.

If I run into any issues, I'll let you know. It looks like their docs for self hosting are pretty barebones so I'll post any updates here

I spent a few hours digging into Unkey and unfortunately don't think it's a good fit for the type of templates I want to maintain.

Happy to pass my notes to anyone else interested in taking it on. Here's what I ran into:

• Non-existent hosting docs: Unkey is open source, but there's no official docs or guidance on hosting it yourself. I ended up reading through their codebase to piece together a working setup. It very much feels like self-hosting isn't an intended use case.

• Requires 3rd party services: Requires Clerk.dev for auth and PlanetScale for the database (they don't officially support standard MySQL/MariaDB). I got it running against MySQL, but I wouldn't count on that remaining viable as they continue development.

It's definitely possible to template this, but given the documentation gaps and required external dependencies to get the whole app running (Dashboard, API, etc), it's not something I want to take on personally. If someone else is comfortable with the Clerk/PlanetScale reqs and is willing to document the setup process themselves, have at it! best of luck 🫡

@mykal appreciate you considering and looking into it. It's definitely a mystery to self-host some of these new-age products with cloud-focus. Checkout this thread - https://github.com/unkeyed/unkey/issues/1964

(Side note - Feels like the "Open Source" tag is just a marketing gimmick. Similar to Unkey, I know more YC companies who advertise themselves as OSS, but you'll almost never be able to figure how to host it and their sales guy will somehow manage to buy the Cloud plan)

Hi, I’ve made a tested, production-ready Railway template for Fusio as an alternative to Unkey:

https://railway.com/deploy/fusio-api-management-platform

Note: on the first startup, it can take a short moment while the database migrations complete.

Hi, I have deployed unkey in Railway. Here is the working template https://railway.com/deploy/unkey?referralCode=tamilarasi

My Template Demo LInk for - https://unkey.up.railway.app/v2/liveness ( will delete this one in 2 days )

Can some one confirm me where it's meet the requiremnt of this thread. Thanks

Per the railway docs there is already a Railway template for Unkey that deploys Unkey + MySQL + Redis.

Deploy using the link below and then set the vars correctly which are

UNKEY_DATABASE_PRIMARY, UNKEY_REDIS_URL, and UNKEY_ROOT_KEY per the template instructions

Deploy and Host Unkey on Railway

https://railway.com/deploy/unkey

Open Railway template: Deploy unkey

Click Deploy Now (it creates Unkey + MySQL + Redis) as shown in the link

Copy vars from redis and MySql

generate a root key

${{random.hex(32)}}

do you mean where the app can run but you dont have to put to put secrets in the environment to use them but on screen import and they work

Hey folks — I think we might be slightly talking past each other, so I want to sanity-check the direction before anyone sinks more hours into this.

From what I’m seeing, the real blocker isn’t Unkey usage itself, but the lack of an opinionated, fail-fast Railway template for self-hosting Unkey with sane defaults.

Concretely, I’d propose:

• An intentionally single-instance, single-region template (no HA, no sharding)

• Railway-managed Postgres as a hard requirement (no SQLite / ephemeral FS)

• Explicit env var validation on boot (DATABASE_URL, UNKEY_MASTER_KEY, JWT secret, etc.)

• A simple healthcheck (/health) so deploys fail loudly instead of half-working

• Clear README scope: what this supports and what it explicitly does not

The goal wouldn’t be “perfect self-hosting,” just one-click deploy that works on first run and makes misconfiguration obvious.

Before going deeper:

Does this align with what you’re trying to ship as a Railway template, or are you aiming for something more flexible / production-HA from day one?

If this direction makes sense, I’m happy to help sketch the exact template structure or review what’s already in progress.