Inquir Compute · A plan is required to run workloads · Free on request

Functions. Your code, on demand.

Long-running AI calls, webhooks and pipelines with scheduled runs, with retries and tracing built in. Start with a function, stay for the application. Node.js, Python, Go or any Dockerfile. No Kubernetes.

Get started
Deploy functions with the CLI →
terminallive

$ inquir deploy

✓ Bundling handler 1.2s

✓ Warm runner ready 0.3s

✓ Deployed ai-summarizer (v3)

$ inquir invoke ai-summarizer \

--payload '{"url": "https://techcrunch.com"}'

{

"summary": "AI funding surges as enterprise adoption...",

"wordCount": 824

} SUCCEEDED · 2.4s

24 h
max time limit per function or step
3
runtimes (JS, Py, Go)
Durable
jobs, retries & DLQ

THE OLD WAY

Shipping one AI feature used to mean five AWS services.

Or — just write the function.

Platform Features

Execution, infrastructure and visibility in one place

One platform for functions, an API gateway, webhooks, pipelines with schedules and container applications. Run full containers and automate recurring work in the same workspace, without managing Kubernetes.

How it works

Your first endpoint in a few minutes: code, deploy, route

Write a function in the browser, deploy it, add a gateway route and call it over HTTPS. A function needs no Dockerfile.

  1. Write

    Write your handler in the browser editor — Node.js, Python, or Go, with syntax highlighting and AI assistance. No local toolchain to set up.

    handler.ts
    export default Handler(async (ctx) => {
      const { url } = await ctx.body;
      return { summary: await ai.summarize(url) };
    });
  2. Deploy

    Click Deploy. The platform builds the container and runs your function; add a gateway route and you have an HTTPS endpoint.

    terminal
    $ inquir deploy
    ✓ Building container        1.2s
    ✓ Warm container ready     0.3s
    ✓ Endpoint ready
  3. Call

    Call it from anywhere with a standard HTTP request. Any language, plain fetch or curl — no proprietary SDK required.

    app.tsx
    const res = await fetch(endpoint, {
      method: "POST",
      body: JSON.stringify({ url })
    });
Get started Docs

A plan is required to run workloads · Free on request

From a function to an HTTPS endpoint

Follow the code, deployment, and request. Explore each step at your own pace.

A guided example of a function deployment.

More than a function runner

Add gateway routes, pipeline schedules, streaming and logs without changing your deployment flow.

main.go
package main

import (
  "context"
  "encoding/json"
  "net/http"
)

func Handler(ctx context.Context, w http.ResponseWriter, r *http.Request) {
  var body map[string]any
  _ = json.NewDecoder(r.Body).Decode(&body)
  w.Header().Set("Content-Type", "application/json")
  _ = json.NewEncoder(w).Encode(map[string]any{
    "runtime": "go",
    "echo":    body,
  })
}

Built for LLM

Made for slow, flaky LLM calls

LLM calls are slow, fail sometimes, and are hard to see into. Inquir handles all three — so you ship integrations instead of plumbing.

Long-running

Minute-long model calls and multi-step chains run to completion — a step's time limit is configurable up to 24 hours.

Traced end-to-end

Every step's input and output, live run status and logs — no observability to wire up yourself.

Durable & reliable

Background jobs with automatic retries, dead-letter, per-key concurrency and idempotency keys.

Use Cases

Use cases: AI agents, webhooks, scheduled pipelines, REST APIs

From AI agents and webhook processors to background jobs and REST APIs — one platform scales with you, from first deploy to production.

Long-running AI workloads, run reliably

Agent loops, RAG pipelines and token streaming that outlast a normal request: minute-long model calls run to completion, with retries and a trace for every step. The OpenAI or Anthropic SDK is one line in inquir.yaml.

LLMRAGStreaming
AI agent backends & tools

Recurring work with pipeline schedules

Add a schedule to a pipeline for reports, syncs and cleanup. Cron expressions, retries and run history are part of the pipeline workflow.

ScheduledSyncETL
Guide to scheduled pipelines

Webhooks processed reliably in the background

Handle Stripe, GitHub, and Slack webhooks reliably: verify signatures, acknowledge fast, and retry idempotently when downstream systems misbehave.

StripeGitHubRetry
Webhook processors & gateway

One workspace

Start with a function. Stay for the application.

A function, a durable job, a pipeline and a container service are four shapes of the same thing: same workspace, same variables, same logs, same team. Reach for the next one when the workload asks for it; nothing gets re-platformed.

Functions

Code the platform runs per invocation: HTTP endpoints, webhooks and background jobs with retries. For recurring work, call the function from a pipeline with a schedule.

Pipelines and durable jobs

Run functions on a schedule or connect them into graphs with retries, branching and approvals. Postgres-backed jobs survive restarts, and execution history shows each step.

Applications

Any container kept running: raw HTTP and TCP, WebSockets, databases on volumes, private networking. Reach for it when the process must stay up, hold state, or speak a protocol of its own.

Comparison

Inquir, AWS Lambda, Cloudflare Workers, Vercel and Modal

APIs, webhooks, scheduled pipelines and background jobs — without Kubernetes.

A snapshot based on each provider's public documentation in 2026. Products and limits change often, so check the provider's current docs before you decide. Most of these platforms now offer scheduled runs; the difference is how many separate products you combine. Inquir keeps container apps, functions, pipelines and their schedules in one workspace behind one gateway.

Feature
Inquir
AWS Lambda
Cloudflare Workers
Vercel
Modal
Runs container images
limited
Scheduled runs

Pricing

Plans with clear limits

Choose Simple or Pro as your project grows, or discuss individual terms with our team. The Free plan is available on request.

Free

Access on request
$0no charge

The Free plan is enabled on request.

Resources for all your workspaces

  • 0.25 vCPU guaranteed, bursts to 0.5 vCPU
  • 512 MB RAM
  • 1 GB storage
  • 2 replicas
  • 2 concurrent functions
  • 1 concurrent build
  • 1 workspace
  • 10K invocations/mo

Free access is granted individually, subject to available capacity.

Simple

$5/ month

For personal projects and small products ready for their next step.

Resources for all your workspaces

  • 0.5 vCPU guaranteed, bursts to 1 vCPU
  • 1 GB RAM
  • 5 GB storage
  • 4 replicas
  • 4 concurrent functions
  • 1 concurrent build
  • 3 workspaces
  • 100K invocations/mo

Enterprise

On-Premise
Custom quote

For organizations with specific resource, deployment and support requirements.

  • Discuss your resource requirements
  • Plan your deployment together
  • Agree on support and service terms
  • Get an individual proposal

In every plan

  • Warm containers
  • API Gateway
  • Pipelines
  • Webhooks

Free, Simple and Pro differ only in resources. Free is available on request; Enterprise terms are agreed individually.

All plans, payment and refund terms

FAQ

Common questions

No. Serverless describes how the code runs. Inquir supports long-running AI calls, webhooks that need a fast acknowledgement and later processing, background jobs, pipelines with schedules and multiple steps, and services that stay up. Runtime, gateway, pipelines, containers, logs and traces share one workspace.

Hi, it's the Inquir Compute team. Ask AI about the product:

Your first endpoint is a few minutes away once you pick a plan.

Plan resources listed up front. No Kubernetes.