... 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 ... ... canonical entry point, or treating custom domains as the primary one? Would love to hear how other builders and users think about this. Comment from Aleksandr Kubarskii(@new_user___1132024007e8749605c4bb9): @sai_tharun_kakirala   Right now