{"id":73177,"title":"🧚 Ergomake - Deploy a staging environment for every pull request","tagline":"Whenever engineers push changes, we deploy their entire application and send them a link.","body":"**TL;DR Ergomake creates a staging environment for each pull request. Every time an engineer pushes changes, we deploy their entire application and send them a link to see it. Our customers use Ergomake for QA, product, and design reviews before any code gets merged.**\n\nHey everyone! We're Lucas and Lucas (yes, Lucas²), the founders of [Ergomake](https://ergomake.dev).\n\n![uploaded image](/media/?type=post\u0026id=73177\u0026key=user_uploads/578593/67fb36be-2271-4b94-8403-f3f1c9bf4612)\n\n**Ergomake creates a new staging environment every time engineers push changes**, making reviews much quicker and easier and helping teams avoid shipping broken changes.\n\n## ❌ The problem: staging is a bottleneck.\n\nEngineers must ship code to a staging environment whenever they need feedback from QAs, designers, and product managers.\n\nThe problem with this approach is that **teams usually have only one staging environment**. Therefore, **engineers scramble to see who will use staging or end up merging changes before anyone else sees them**.\n\n![uploaded image](/media/?type=post\u0026id=73177\u0026key=user_uploads/578593/0d929f46-4a46-425d-86e8-458fc4843816)\n\n**Consequently, teams slow down, applications break, or undesirable code gets shipped**.\n\nWhen that happens, engineers rush to fix the broken code already merged. For that, they must go through the whole review process again, which is a massive waste of time and money.\n\n## 💡 The solution: everyone gets their own staging.\n\nWith Ergomake, every change gets deployed to a new staging environment.\n\n![uploaded image](/media/?type=post\u0026id=73177\u0026key=user_uploads/578593/dc0ff32d-60c5-46d1-a759-b875aaaaea15)\n\nThat way, engineers can get input from the rest of their team without queueing to use staging.\n\nAdditionally, by getting reviews _before_ deploying code, teams avoid merging all sorts of undesirable changes. Consequently, they avoid bugs and reduce rework by keeping `main` always working.\n\nWith Ergomake, teams can merge straight into `main` because they do all their manual testing and validations within their pull requests. Therefore, these teams avoid complicated branching strategies and painful integration cycles.\n\n![uploaded image](/media/?type=post\u0026id=73177\u0026key=user_uploads/578593/9b319d08-4e0e-4239-9786-f5cc9373d979)\n\n## ⚙️ How does it work?\n\nErgomake integrates with GitHub and gets notified whenever someone opens a pull request.\n\nWhen that happens, Ergomake uses the `docker-compose.yaml` file within the repository to deploy your application on our infrastructure.\n\nOnce Ergomake has spun everything up, it adds a comment to the pull request containing the link to test your application.\n\nOur previews can include databases, and they support all types of projects, including those spread across multiple repos.\n\n## ➡️ The ask: sign-up now (there's a free tier)\n\n**You can sign-up for Ergomake at **[**app.ergomake.dev**](https://app.ergomake.dev)**.** There, you'll be able to configure previews for any repositories you want for free.\n\n**If you prefer, we're happy to do all the integration for you or hop on a call and guide you through the process**. If you think that could be helpful, [book an intro call here](https://calendly.com/lucasfcosta/ergomake-15-minutes).\n\nFor anything else, [we're also on Discord](https://discord.gg/daGzchUGDt).","slug":"J2H-ergomake-deploy-a-staging-environment-for-every-pull-request","created_at":"2023-07-18T15:59:24.172Z","updated_at":"2026-05-01T09:39:34.405Z","total_vote_count":85,"url":"https://www.ycombinator.com/launches/J2H-ergomake-deploy-a-staging-environment-for-every-pull-request","share_image_url":"//bookface-static.ycombinator.com/assets/ycdc/yc-og-image-c440a0ad1dacfb86eeeb343717479cc54d256614449b4ef719977a0a451f8bc8.png","company":{"id":28868,"name":"Briefer","slug":"briefer","url":"https://briefer.cloud","logo":"https://bookface-images.s3.amazonaws.com/small_logos/1e589854f66150c916444527d7f4aa314d3961ed.png","batch":"Summer 2023","industry":"B2B","tags":["Developer Tools","B2B","Data Science","Data Engineering","Data Visualization"],"search_path":"https://bookface.ycombinator.com/company/28868"}}