Inquir Compute Marketplace: ship proven serverless stacks faster
The Marketplace is a curated catalog of deployment-ready templates—each bundle describes functions, API gateway routes, scheduled pipelines, and the secrets you wire before provision. Pick a pattern, configure keys in the deploy wizard, and land in the IDE with runnable code instead of an empty repo.
Last updated: 2026-05-11
- Official templates maintained against current runtimes
- Partner packs for integrations and vertical starters
- Provision flows into an existing workspace from the console
Answer first
Direct answer
Inquir Compute Marketplace: ship proven serverless stacks faster. Each listing summarizes what you get—function count, routes, pipelines/jobs, declared secrets—before you spend time reading source. The deploy wizard walks workspace selection, secret capture, validation, and provision so the artifact matches Inquir’s Lambda-compatible execution model.
When it fits
- You want an opinionated layout for Stripe, Slack, GitHub, agents, or data sync without authoring every route and pipeline by hand.
- You are onboarding engineers who learn faster from runnable samples tied to real ingress rules.
Tradeoffs
- A ZIP file without an automated provision step still leaves route tables, cron expressions, and environment contracts manual—exactly where mistakes duplicate webhooks or leak credentials.
- Surface-level “starters” that omit gateway auth or pipeline schedules push complexity back into tribal knowledge instead of executable infrastructure.
Workload and what breaks
Blank functions hide weeks of glue work
Production-grade handlers need routing rules, auth surfaces, pipeline triggers, and secret hygiene—not only a single `handler.ts`. Teams repeatedly rebuild the same scaffolding for Stripe webhooks, hourly sync jobs, or agent tool APIs.
Copying random repos forks dependency drift: README promises features your gateway never wired, runtime pins disagree with the platform, and observability hooks never land.
Trade-offs
Templates only help when provisioning matches the platform
A ZIP file without an automated provision step still leaves route tables, cron expressions, and environment contracts manual—exactly where mistakes duplicate webhooks or leak credentials.
Surface-level “starters” that omit gateway auth or pipeline schedules push complexity back into tribal knowledge instead of executable infrastructure.
How Inquir helps
Marketplace templates align with gateway, pipelines, and layers
Each listing summarizes what you get—function count, routes, pipelines/jobs, declared secrets—before you spend time reading source. The deploy wizard walks workspace selection, secret capture, validation, and provision so the artifact matches Inquir’s Lambda-compatible execution model.
Official templates track Node.js 22, Python 3.12, and Go 1.22 conventions used across the product; partner pages group recommended bundles so you can evaluate vendors alongside maintained starters.
After provision you land in the browser IDE next to the same deploy and execution history tools you use for hand-written functions—templates are a shortcut, not a separate runtime.
What you get
What you can expect from the Marketplace
Searchable catalog
Filter and discover templates by workload—agents, webhooks, cron, APIs—with clarity on runtime, difficulty, and setup time estimates where publishers provide them.
Transparent resource summaries
Cards show how many functions, gateway routes, pipelines, and scheduled jobs ship with the bundle so capacity planning starts before deploy.
Guided deploy wizard
Authenticate, choose a workspace, enter required secrets, validate configuration, then execute provisioning—reducing “works on my laptop” drift.
Partner storefronts
Partner profile pages highlight official versus community recommendations so teams can compare publishers without leaving the console.
What to do next
From Marketplace listing to first invoke
Use the console catalog once your workspace exists.
Register and create a workspace
Marketplace flows assume an authenticated account with at least one workspace to receive resources.
Open `/marketplace` in the console
Browse templates, read detail pages for secrets and demos, then start deploy when the fit is clear.
Configure secrets and provision
Complete validation errors before executing deploy; afterward open functions from Executions or the IDE to run tests.
Explore
Continue learning after you pick a template
These guides deepen patterns that Marketplace bundles automate—gateway behavior, browser deploy ergonomics, and representative use cases.
Code example
How a template describes infrastructure
Listings carry structured summaries (not arbitrary README prose). The JSON below illustrates the kind of metadata you review before committing secrets.
{ "template": "stripe-webhook-processor", "runtime": "nodejs22", "resourceSummary": { "functions": 2, "routes": 1, "pipelines": 1, "jobs": 0 }, "requiredSecrets": ["STRIPE_WEBHOOK_SECRET"] }
When it fits
When the Marketplace is the right entry point
When this works
- You want an opinionated layout for Stripe, Slack, GitHub, agents, or data sync without authoring every route and pipeline by hand.
- You are onboarding engineers who learn faster from runnable samples tied to real ingress rules.
When to skip it
- You need bespoke compliance guarantees from a partner template—review vendor docs and run your own security assessment.
FAQ
FAQ
Is the Marketplace the same URL as the public marketing site?
This page explains the product surface area. The interactive catalog lives at `/marketplace` inside the authenticated console.
Can I edit code after a template deploys?
Yes. Provisioned assets behave like any other workspace functions—iterate in the IDE, redeploy, and monitor executions normally.
Do templates replace writing infrastructure documentation?
They accelerate setup, but you should still document environment-specific values, data flows, and operational runbooks for your team.