For anyone who want to support
https://www.producthunt.com/prod...

I like Lambda for a lot of things, but there s a very specific point where it stops feeling elegant.

Usually it starts with something like:

• a job that runs too long

• a workflow that should keep going in the background

• a task that needs better isolation or custom runtime behavior

• a system that starts needing cron, retries, webhooks, logs, and routing in one place

And then the answer often becomes: move to Fargate, ECS, Step Functions, EC2, or stitch multiple services together.

Not to sell aggressively.
To understand where the current stack still feels fragmented.
We re building Inquir Compute 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 in how you handle execution today.

Created a very simple app to gather feedback about Inquir.
In case you find bugs, or just want to see any new features, add them all here.
It's not modarated XD.

One thing we think is still underrated in compute platforms is observability.

A lot of infra feels simple until something 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 Inquir Compute, 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, and what happened right before the failure.

We recently implemented custom domain support in Inquir Compute, 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?

• What parts are usually the hardest in practice: DNS flow, TLS issuance, routing, verification, or UX?

• Do you prefer keeping platform subdomains as the canonical entry point, or treating custom domains as the primary one?

Hi everyone,

I m getting ready to launch Inquir Compute.

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.

I m curious what languages people actually prefer for serverless workloads today.

When you build functions for cron jobs, APIs, background tasks, or AI-related workflows, what do you usually choose first and why?

Is it:

• Node.js for speed of development

• Python for AI/data tasks

• Go for performance and simplicity

• something else