What would make Temps better for you? Share your feedback

[dviejokfs]

Hey everyone 👋

We're building Temps to be the self-hosted platform that replaces your deployment stack, analytics, error tracking, session replay, and monitoring — all in a single binary.

We'd love to hear from you to make sure we're building the right things. If you've tried Temps (or are considering it), drop a comment answering any of these:

1. What brought you here?
What made you look into Temps? Cost, self-hosting, simplifying your stack, something else?

2. What are you running on it?
Side projects, production apps, internal tools? What kind of stack (Next.js, Go, Docker, etc.)?

3. What's working well?
Anything you particularly like about the experience so far.

4. What's missing or frustrating?
Rough edges, missing features, things that made you consider going back to another tool. Be honest — this is the most useful part.

5. What should we prioritize next?
If you could pick one area for us to focus on, what would it be?

• Deployments & environments
• Web analytics
• Session replay
• Error tracking
• Uptime monitoring
• Managed databases
• Transactional email
• Something else entirely

No format required — just comment with whatever is on your mind. Short answers are perfectly fine.

Thanks for being early users. Your feedback directly shapes what we build next.

[camflan]

ARM-64 support would be awesome

[dviejokfs]

@camflan do you mean linux arm64?

[BaptisteCrouzet]

Multi-node / High Availibility is game changer for me

[lostb1t]

for one, should be a tad easier to spin up a test env

tried the script but requires a domain. Just wanna test it without setting up a domain and dns records

tried it manually but when starting i get:

Error: Failed to start proxy server: Failed to register GeoPlugin: Plugin registration failed for 'geo': Other error: Failed to open MaxMind database at '/xxxxxx/GeoLite2-City.mmdb': i/o error: No such file or directory (os error 2)

so i gave up

[dviejokfs]

Hi @lostb1t thanks for the feedback

For the domains, I will add the reason why we require a wildcard domain to the deploy.sh script. It's a one time operation needed to be able to deploy any future application without manual work for each domain. I understand it's an extra step that Coolify/Dokploy doesn't have, but in return it allows you to move fast with multiple projects/environment with a closer experience to Vercel/Railway/Render.

About the GeoPlugin error, it will be fixed in the next release (already available in v0.1.0-beta.16) to auto download GeoLite2-City.mmdb on startup if it's not found.

[lostb1t]

i understand the reason, like i said, when coming across a new project like this inwant to spin it up fast and just be able to test basic functionality / browse the ui without having to setup a domain and necessary dns redords for deployment as its just testing. Lots of similar projects dont make this a requirement for setup and just allow setting it during runtime.

just my 2 cents

[dviejokfs]

Would a hosted read only demo help? Or optional domain setup when setting up temps

[lostb1t]

Would a hosted read only demo help? Or optional domain setup when setting up temps

yeah for sure

[lostb1t]

Something like crowdsec builtin would be nice (optional ofcourse)

think pangolin has it aswell

[joeblew999]

I use hetzner servers for container stuff and Cloudflare for the things that can’t run on Cloudflare and need fast edge .

There might be opportunities for some integration aspects . Maybe a plugin or just docs

[trinvh]

Deployments & environments
I've been trying to deploy a docker only project but it was hard for me to find a working way and I almost gave up

[dviejokfs]

I'm working on improvements to make deployment of temps 10x easier and also deployment easier.

What version are you running?

[trinvh]

@dviejokfs I ended up switching to Dokploy for now. However, I still think your platform has a lot of advantages, so I'm looking forward to a significant update from your side.

The main blocker for me at the moment is support for deploying projects that are already defined as raw Docker Compose stacks, similar to what Dokploy supports. As soon as I can deploy those projects directly, I'd be happy to move back.

[dviejokfs]

version 0.1.0 will make the experience of getting from 0 -> 1 way faster. I'll post here as soon as that happens so that you can give it a try.