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.

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

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.