... InquirCompute launches on Product Hunt today at 12:01 AM Pacific. The new release brings container apps and databases alongside functions and scheduled workflows. You can put a web app, its Postgres database and background work in one workspace, then follow releases and logs from the console or CLI. You can start with: A web app and its database. An internal tool for your team. A background worker or scheduled task. There is a Free plan available on request ... ... from a local project to a running app? Launch page Comment from Aleksandr Kubarskii(@al_kub): For ffmpeg I would use a container worker. Applications have no idle timeout and you can stream logs while they run with

... launching the new version of InquirCompute on Product Hunt today. It started as a serverless runtime. This release adds container apps and databases, so a web app, its database and background work can live in one workspace. Deploy from GitHub, a Dockerfile or a container image. Connect Postgres or Redis over a private network. Run functions and scheduled workflows alongside your app. Check releases and logs from the console or CLI. I d like feedback on the first deployment ...

... everything for later Allow one exception Ask them to upgrade Each choice has a cost for the person using it and the person running it. Showing the limit earlier would help too. I m interested in this while building InquirCompute. Where do you draw that line in your own product? A concrete example would help: what limit did someone hit, and what could they do next? Comment from Aleksandr Kubarskii(@al_kub): @ksanyokm   I would label that score ...

... first screen asks you to create an account before you can see what it does. Some apps need an account to save work or sync; for a quick evaluation, that s a real ask. As someone building InquirCompute, I m curious about that first step. The difference may be whether you reach a useful moment before sharing an email, or whether signing up is itself part of getting value. Do you prefer a guest or demo mode first ...

... work feels like another project. The awkward part might be: Years of files or history you need to keep. A team that already knows the old workflow. Connections to other tools you would have to rebuild. I am building InquirCompute, so I am interested in what makes trying a new app or platform worth the effort of switching. What kept you in an app you wanted to leave, and what finally made switching worthwhile? A specific example would help ... ... work, where I need to be ready to shift quickly if I want to maintain the efficiency. Otherwise, I often find myself reaching for the app I got used to even after downloading a more convenient or advanced

... open an app to finish one awkward job, get the result, and might not need it again for a month. A monthly plan can feel expensive for that pattern, even when the app saves real time. The alternatives have their own tradeoffs: Keep a subscription for convenience. Pay per task or buy credits. Use a free tool and accept extra steps. Which app do you happily pay for despite rarely opening it, and what makes it worth keeping? A specific ... ... would help: what is the job, and how does the app charge for it? Comment from Aleksandr Kubarskii(@al_kub): @jaewon_seo  maybe this can be useful for you? https://everything-yu5xkw.apps.i... you can actually deploy it yourself from Inquir

... over. Sometimes doing it yourself is how you notice a problem or understand what someone actually needs. A few examples: Replying to a frustrated customer. Checking an app before sharing it. Deciding what to build next. I am building InquirCompute for apps, databases and background jobs, so I am curious about where people draw that line. What is one task you deliberately keep manual, and what would need to change before you trusted AI with it? Comment from Aleksandr ...

... user uploads a file, starts an export, and closes the tab. The work may still be running, but when they come back, they need to know what happened. I am building InquirCompute for apps, databases and background jobs. I am interested in the part users see, beyond whether the job itself succeeds. There are a few options: A simple waiting screen. A task page they can return to. A notification when the result is ready. What approach worked ...

... want to step away for the weekend. What would you check before closing the laptop? An alert that reaches you when something fails A backup you have actually restored A limit on unexpected spending I am building InquirCompute, so I am interested in this part of running an app: knowing when it needs your attention without watching a dashboard all day. What made the biggest difference to your confidence leaving an app unattended? Share one check or habit ...

... well and still feel unfinished. There is always something else you could add: Team accounts Billing Integrations A better onboarding flow Each one sounds reasonable, but together they can move the launch further away. I am preparing InquirCompute for launch, and I am curious how other makers draw that line. What did you deliberately leave out before your first users arrived? Was it something they later asked for, or something you never needed to build? Share one feature ...

... recently built a small PDF editor with AI for myself. That got me wondering about another use for these small apps. Has anyone here built a free tool specifically to help people discover their main product? I m getting InquirCompute ready to launch. It s a platform for running apps, databases and background jobs, and it s where I host the editor. Alongside sharing what I m building here, I m looking at other ways to reach developers ... ... sits directly before the review-room step. I ve shared it in relevant workflow discussions, but I haven t verified that it brings customers yet. I m keeping tool use, review-room visits, signups and genuine payments separate. For

... reading about a product to actually trying it. For those who ve launched something: where did your first users come from? Were they following what you were building, or did you find them somewhere completely different? I m getting InquirCompute ready to launch. It s a platform for running apps, databases and background jobs. I ve been sharing what I m working on here, but I m still figuring out how to reach the people who might ...

... what people here are working on before the demo is polished. A screenshot or a link is enough, along with what it does and the next thing you re trying to get working. I m preparing to launch InquirCompute, a platform for running apps, databases and background jobs. In my last post, I asked about tools people had built for themselves with AI. This time, I m interested in the projects that are still in progress. What works already ...

... work. I suspect a lot of useful AI-built software will end up as something someone keeps in their bookmarks and uses every week, without ever trying to turn it into a business. I m hosting the editor on InquirCompute, the platform I m building for apps, databases and background jobs. We re getting close to launch, and I d like to hear about the things people are building for themselves. What s the most oddly specific tool ... ... exactly what you need than to keep paying for another subscription. Comment from Aleksandr Kubarskii(@al_kub): @alexander_wright6  in case you want it to go online, let me know, I'll help you to deploy it with

... building InquirCompute, a platform for running apps, databases and background jobs in one workspace. AI tools are helping more people write working applications. I m interested in what happens next, when you need to put that app online and keep it running. If you ve deployed something you built with AI, where did you get stuck? Build errors, database connections, environment variables, unexpected costs or something else? Tell me what you built, where you deployed it and what took ... ... longer than expected. I d like to use those examples to decide what to improve in

... with an idea of who the product is for, but real users always end up challenging it For me, the most interesting part is seeing who actually pays for it and why. Comment from Aleksandr Kubarskii(@al_kub): With InquirCompute I am aiming at developers who need a place to run their apps databases and background jobs Still figuring out which of those needs is the strongest reason to choose it Developers is a pretty broad audience ... ... Pinateca. A client was paying a lot for a form tool and wanted to cut that, which turned into Halict. And when Sidekick, which I loved, shut down, I made SpaceDeck. I've also got Mailchimp, ClickFunnels and Kajabi

... sell aggressively. To understand where the current stack still feels fragmented. We re building InquirCompute for teams that need a better way to run triggered, container-based, production-ready workloads without stitching together too many separate tools. If that sounds close to your world, I d love to compare notes on what s working, what s painful, and what still feels missing in the market. Comment or message me with your stack I m especially interested ...

... everyone, I m getting ready to launch InquirCompute . It s a serverless platform for AI agents, cron jobs, webhooks, and backend functions, with isolated containers, custom domains, and deployment on your own server. I d love feedback from anyone who has run into limits with managed serverless or edge runtimes. A few questions I d especially like help with: - Does the value proposition make sense? - What use case sounds most compelling? - What would stop you from trying something like ... ... that point, you re already in production and the compromises become very real. My view is: Modal is great when

... breaks in production. A webhook fails, a cron job doesn t run, an AI agent gets stuck, or a function times out even though it worked fine in testing. That is where just running code stops being enough. In InquirCompute , we think logs and observability are a core part of the product, because developers need more than raw output. They need context: what triggered the execution, which route or webhook was involved, how long it ran, whether it retried ...

... tasks Go for performance and simplicity something else I d also love to know what matters most in practice: startup time developer experience ecosystem debugging deployment simplicity performance in production We re thinking a lot about this while building InquirCompute , so I d love to hear real preferences from developers here ...

... recently implemented custom domain support in InquirCompute , and it feels like one of those features that really changes a platform from works technically to ready for production. For me, custom domains are a core part of production-grade infrastructure. They are not just cosmetic they affect branding, trust, onboarding, and the overall developer experience. I d be curious how others think about this in serverless and deployment platforms: At what point do you consider custom domains a must-have ... ... assistant launching on PH April 10th). For onboarding, the difference between a branded domain and a random cloud subdomain is night and day. On the infra side, TLS issuance is usually the hairiest part, especially at scale. Does

... Remote teamwork? Get it Dun! https://www.producthunt.com/prod... Comment from Jemmy(@amiaomomo): Tampo-Let the hearing-impaired touch music. https://www.producthunt.com/prod... Comment from Shivam Singh(@whatshivamdo): Shram.io - People-first work management tool. Comment from Aleksandr Kubarskii(@al_kub): InquirCompute - build, deploy, monitor Comment from Ivan(@pricepilot): PricePilot A jest pitch: Trustworthy price comparison unlike Honey Actual pitch: Price comparison made for people https://trypricepilot.com Comment from Dan ZeruApps(@daniel_zeru_apps): BrandBay - Brand asset management made simple :) Comment ...