[PR #672] Add Temps to PaaS #5272

New Issue

GiteaMirror · 2026-04-27T09:35:06-05:00

GiteaMirror commented

2026-04-27 09:35:06 -05:00

📋 Pull Request Information

Original PR: https://github.com/awesome-foss/awesome-sysadmin/pull/672
Author: @dviejokfs
Created: 2/17/2026
Status: 🔄 Open

Base: master ← Head: add-temps-to-paas

📝 Commits (2)

46ee0e8 Add Temps to PaaS
eded71e Update Temps description to mention Vercel/Railway/Render alternative

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

Your additions are Free software
Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
Submit one item per pull request. This eases reviewing and speeds up inclusion.
Format your submission as follows, where Demo and Clients are optional.
Do not add a duplicate Source code link if it is the same as the main link.
Keep the short description under 80 characters and use sentence case
for it, even if the project's webpage or readme uses another capitalisation.
Demo links should only be used for interactive demos, i.e. not video demonstrations.
- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
Additions are inserted preserving alphabetical order.
Additions are not already listed at awesome-selfhosted
The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
You have searched the repository for any relevant issues or PRs, including closed ones.
Any category you are creating has the minimum requirement of 3 items.
Any software project you are adding to the list is actively maintained.
The pull request title is informative, unlike "Update README.md".
Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
"Remove aaa from bbb" for removing, "Fix license for aaa", etc.

Why is it awesome?

Temps is a self-hosted deployment platform built in Rust that consolidates what typically requires multiple SaaS tools (Vercel + Sentry + Plausible + managed DBs) into a single binary. It provides git push-to-deploy with automatic framework detection, built-in web analytics, error tracking (Sentry-compatible), session replay, managed PostgreSQL/Redis/MongoDB, S3-compatible storage, automatic TLS via Let's Encrypt, and zero-downtime rollouts. It supports Next.js, Vite, Go, Python, Rust, Java, .NET, and Docker. Dual-licensed under MIT/Apache 2.0.

Have you used it? For how long?

Yes, I've been using Temps for several months to deploy and manage web applications in production.

Is this in a personal or professional setup?

Both personal projects and professional production workloads.

How many devices/users/services/... do you manage with it?

Multiple web applications across different environments (staging/production), with managed database instances and monitoring for each.

Biggest pros/cons compared to other solutions?

Pros: Single binary deployment (no complex Docker Compose stacks), built-in observability (analytics + error tracking + session replay) eliminates the need for separate tools, Rust-based so very resource efficient, Pingora-powered reverse proxy handles TLS automatically, managed databases are provisioned alongside apps. Compared to Coolify or Dokku, the integrated observability stack is a major differentiator.

Cons: Newer project compared to established alternatives like Dokku or CapRover, so the community is still growing.

Any other comments about your use case, things you've found excellent, limitations you've encountered... ?

The single-binary approach makes installation and upgrades straightforward. The built-in analytics and error tracking are production-quality and eliminate the need to self-host separate tools like Plausible and Sentry. The MCP (Model Context Protocol) integration for AI-assisted development workflows is a unique and forward-looking feature.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/awesome-foss/awesome-sysadmin/pull/672 **Author:** [@dviejokfs](https://github.com/dviejokfs) **Created:** 2/17/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `add-temps-to-paas` --- ### 📝 Commits (2) - [`46ee0e8`](https://github.com/awesome-foss/awesome-sysadmin/commit/46ee0e8ee8c7ff1ee9bf7835945ab739a0a66781) Add Temps to PaaS - [`eded71e`](https://github.com/awesome-foss/awesome-sysadmin/commit/eded71ed9074b70a3c40fcd4b879e70305e45a46) Update Temps description to mention Vercel/Railway/Render alternative ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description  Thank you for taking the time to work on a PR for Awesome-Sysadmin! To ensure your PR is dealt with swiftly please check the following: - [x] Your additions are [Free software](https://en.wikipedia.org/wiki/Free_software) - [x] Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts). - [x] Submit one item per pull request. This eases reviewing and speeds up inclusion. - [x] Format your submission as follows, where `Demo` and `Clients` are optional. Do not add a duplicate `Source code` link if it is the same as the main link. Keep the short description under 80 characters and use [sentence case](https://en.wikipedia.org/wiki/Letter_case#Sentence_case) for it, even if the project's webpage or readme uses another capitalisation. `Demo` links should only be used for interactive demos, i.e. not video demonstrations. ``- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language` `` - [x] Additions are inserted preserving alphabetical order. - [x] Additions are not already listed at [awesome-selfhosted](https://awesome-selfhosted.net) - [x] The `Language` tag is the main **server-side** requirement for the software. Don't include frameworks or specific dialects. - [x] You have searched the repository for any relevant [issues](https://github.com/awesome-foss/awesome-sysadmin/issues) or [PRs](https://github.com/awesome-foss/awesome-sysadmin/pulls), including closed ones. - [x] Any category you are creating has the minimum requirement of 3 items. - [x] Any software project you are adding to the list is actively maintained. - [x] The pull request title is informative, unlike "Update README.md". Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb, "Remove aaa from bbb" for removing, "Fix license for aaa", etc. -------------- - **Why is it awesome?** Temps is a self-hosted deployment platform built in Rust that consolidates what typically requires multiple SaaS tools (Vercel + Sentry + Plausible + managed DBs) into a single binary. It provides git push-to-deploy with automatic framework detection, built-in web analytics, error tracking (Sentry-compatible), session replay, managed PostgreSQL/Redis/MongoDB, S3-compatible storage, automatic TLS via Let's Encrypt, and zero-downtime rollouts. It supports Next.js, Vite, Go, Python, Rust, Java, .NET, and Docker. Dual-licensed under MIT/Apache 2.0. - **Have you used it? For how long?** Yes, I've been using Temps for several months to deploy and manage web applications in production. - **Is this in a personal or professional setup?** Both personal projects and professional production workloads. - **How many devices/users/services/... do you manage with it?** Multiple web applications across different environments (staging/production), with managed database instances and monitoring for each. - **Biggest pros/cons compared to other solutions?** Pros: Single binary deployment (no complex Docker Compose stacks), built-in observability (analytics + error tracking + session replay) eliminates the need for separate tools, Rust-based so very resource efficient, Pingora-powered reverse proxy handles TLS automatically, managed databases are provisioned alongside apps. Compared to Coolify or Dokku, the integrated observability stack is a major differentiator. Cons: Newer project compared to established alternatives like Dokku or CapRover, so the community is still growing. - **Any other comments about your use case, things you've found excellent, limitations you've encountered... ?** The single-binary approach makes installation and upgrades straightforward. The built-in analytics and error tracking are production-quality and eliminate the need to self-host separate tools like Plausible and Sentry. The MCP (Model Context Protocol) integration for AI-assisted development workflows is a unique and forward-looking feature. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-27 09:35:06 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sysadmin#5272