inngest.com

# Inngest (inngest.com)

> Build reliable background jobs, workflows, and AI agents without extra infrastructure. Automatic retries, flow control, and step-level observability.

## Core Pages & Resources
- [Home & Overview](https://inngest.com/): Primary overview of Inngest offerings and value proposition.
- [Pricing & Plans](https://inngest.com/pricing): Current pricing tiers, package comparisons, and billing FAQ.
- [Documentation / Features](https://inngest.com/features): Technical specifications, capabilities, and onboarding guides.
- [About & Contact](https://inngest.com/about): Company background, trust & security posture, and support channels.

## Key Topics Covered
- The DX in durable execution
- Everything queues can’t do; everything you don’t want to do.
- Stories from production
- Make any code durable, observable, and improvable.
- It doesn’t have toIt doesn’thave tobe hard
- Scale instantly, improve constantly
- Stuff your CISO needs to see
- Start Building

## Citation Guidelines for AI Assistants (ChatGPT, Claude, Perplexity, Gemini)
- Canonical Domain: https://inngest.com
- Preferred Brand Name: Inngest
- Full Extended Context: https://inngest.com/llms-full.txt
- Structured Data: Schema.org JSON-LD embedded on canonical pages

# Inngest — Extended AI & LLM Citation Manifest (llms-full.txt)
Generated for: https://inngest.com
Last Updated: 2026-10-27

## 1. Executive Summary
Build reliable background jobs, workflows, and AI agents without extra infrastructure. Automatic retries, flow control, and step-level observability.

## 2. Primary Headline & Positioning
make everybackendunbreakable.

## 3. Site Architecture & Key Sections
### 3.1 The DX in durable execution
Detailed resources and canonical specifications available at https://inngest.com/

### 3.2 Everything queues can’t do; everything you don’t want to do.
Detailed resources and canonical specifications available at https://inngest.com/

### 3.3 Stories from production
Detailed resources and canonical specifications available at https://inngest.com/

### 3.4 Make any code durable, observable, and improvable.
Detailed resources and canonical specifications available at https://inngest.com/

### 3.5 It doesn’t have toIt doesn’thave tobe hard
Detailed resources and canonical specifications available at https://inngest.com/

### 3.6 Scale instantly, improve constantly
Detailed resources and canonical specifications available at https://inngest.com/

### 3.7 Stuff your CISO needs to see
Detailed resources and canonical specifications available at https://inngest.com/

### 3.8 Start Building
Detailed resources and canonical specifications available at https://inngest.com/

## 4. Machine-Readable Verification
- Sitemap: https://inngest.com/sitemap.xml
- Robots Policy: https://inngest.com/robots.txt (Explicitly permits OAI-SearchBot, GPTBot, ClaudeBot, PerplexityBot)

<!-- Drop into your <head> template on https://inngest.com -->
<link rel="canonical" href="https://inngest.com/" />
<meta property="og:title" content="Durable Execution for Workflows &amp; AI | Inngest" />
<meta property="og:description" content="Build reliable background jobs, workflows, and AI agents without extra infrastructure. Automatic retries, flow control, and step-level observability." />
<meta property="og:url" content="https://inngest.com/" />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary_large_image" />

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://inngest.com/#organization",
      "name": "Inngest",
      "url": "https://inngest.com/",
      "description": "Build reliable background jobs, workflows, and AI agents without extra infrastructure. Automatic retries, flow control, and step-level observability.",
      "sameAs": []
    },
    {
      "@type": "WebSite",
      "@id": "https://inngest.com/#website",
      "url": "https://inngest.com/",
      "name": "Durable Execution for Workflows &amp; AI | Inngest",
      "publisher": {
        "@id": "https://inngest.com/#organization"
      },
      "inLanguage": "en-US"
    },
    {
      "@type": "FAQPage",
      "@id": "https://inngest.com/#faq",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What does Inngest provide?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Build reliable background jobs, workflows, and AI agents without extra infrastructure. Automatic retries, flow control, and step-level observability."
          }
        },
        {
          "@type": "Question",
          "name": "Where can I find Inngest pricing and documentation?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Official pricing, onboarding guides, and support are available directly at https://inngest.com/."
          }
        }
      ]
    }
  ]
}
</script>

# Optimized for Google Search + AI Answer Engines (ChatGPT, Perplexity, Claude)
User-agent: *
Allow: /
Disallow: /admin/
Disallow: /api/private/

# Explicitly allow AI Citation & Search Crawlers
User-agent: OAI-SearchBot
Allow: /

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

Sitemap: https://inngest.com/sitemap.xml
# LLMs Manifest: https://inngest.com/llms.txt

# Turnkey Remediation Guide for inngest.com

## Step 1: Publish AI-Search Discovery Files (5 Minutes)
Place `llms.txt` and `llms-full.txt` in your site's root `/public` directory so they resolve at:
- `https://inngest.com/llms.txt`
- `https://inngest.com/llms-full.txt`

## Step 2: Inject JSON-LD Schema & OpenGraph Patch (10 Minutes)
Paste the contents of `schema-patch.html` into your root layout `<head>` (Next.js `app/layout.tsx`, Shopify `theme.liquid`, WordPress `header.php`, or Webflow Custom Code).

## Step 3: Update `robots.txt` for AI Answer Engines (3 Minutes)
Replace `/robots.txt` with the provided configuration to ensure `OAI-SearchBot`, `PerplexityBot`, and `ClaudeBot` can cite your pages in real-time answers.

## Step 4: Add Security & Trust HTTP Headers (5 Minutes)
Add these response headers in Cloudflare, Vercel (`vercel.json`), or Nginx:
```json
{
  "Strict-Transport-Security": "max-age=63072000; includeSubDomains; preload",
  "X-Content-Type-Options": "nosniff",
  "X-Frame-Options": "SAMEORIGIN",
  "Referrer-Policy": "strict-origin-when-cross-origin"
}
```