What if the automated build doesn't fit my stack?

The questionnaire catches common mismatches and steers you to Custom before you pay.

Which Git providers do you support?

All of them. We deliver a Git-applicable patch file that works for GitHub, GitLab, Bitbucket, Azure DevOps, and self-hosted Git. Your team applies it locally with `git am` and reviews via your normal PR workflow. We never need direct access to your repo.

Do you need write access to my repo?

No. The patch-file delivery model means we never touch your code directly. Many B2B security teams prefer this — fewer external service accounts with repo access is a security improvement, not a limitation. (If you're on the Custom tier and want us to open the PR for you, that can be arranged during the scoping call with a temporary deploy key.)

$1,299 · delivered in <24 hours

The reason agents don't mention you is fixable in one merge.

The whole agent-discoverability stack as a patch file, reviewed in your repo's normal workflow. No deploy keys, no service accounts.

Pay

$1,299 via Dodo

Questionnaire

5 questions, ~3 minutes

Pipeline

build runs, email progress

Patch

<24h · git am-applicable file

Buy Implementation — $1,299 Need something custom? See the Custom tier →

patch · astrant-implementation.patchRepresentative sample

From: Astrant <implementation@astrant.io>
To: you@sample-saas.example
Subject: [PATCH] astrant implementation — sample-saas.example

 public/llms.txt                  | 48 ++++++++++++
 public/openapi.yaml              | 63 +++++++++++++++
 app/layout-jsonld.html           | 21 ++++++
 mcp-server/index.ts              | 84 +++++++++++++++++++
 mcp-server/wrangler.jsonc        | 18 ++++
 mcp-server/package.json          | 12 +++
 mcp-server/README.md             | 27 ++++++
 monitoring/check-llms-txt.sh     | 12 +++
 monitoring/check-mcp-server.sh   | 14 +++
 ASTRANT_IMPLEMENTATION.md        | 39 +++++++++
 10 files changed, 338 insertions(+)

→ git am astrant-implementation.patch
→ review diff · merge

The full standard stack

llms.txt

Generated from your sitemap and homepage content. Curated, not dumped. Scored against our own rubric before delivery.

MCP Server

Hosted at mcp.yourdomain.com (you point the CNAME). Baseline tools: get_capabilities, get_pricing, get_services, book_demo, check_llms_txt, plus anything inferable from your pricing page.

OpenAPI spec

Generated from your public API if detectable; skipped otherwise.

JSON-LD schema

Organization, Service, Offer, FAQPage injected into your key pages. Delivered as part of the Git-applicable patch you receive via email — works with any Git provider, no repo access from us required.

Baseline monitoring

Worker deployed to ingest your site's Cloudflare logs and parse AI user-agents + referrers. Dashboard URL delivered with the build.

Handoff documentation

README included in the patch, explaining what was built and how to modify it. Lands in your repo when your team applies the patch.

What you're buying

Your $1,299 Implementation includes

• A git am-applicable patch with deployable MCP server code, llms.txt, OpenAPI, JSON-LD, and monitoring scripts
• One-command deploy wrapper (npx @astrant/deploy-mcp) on the roadmap; deploy today with wrangler deploy
• 90 days of citation-tracking probes across 4 major-model providers
• 3 follow-up audits at Day 30, Day 60, Day 90
• Standard continuation option at Day 90 ($149/mo) for ongoing measurement

Not open for purchase yet

Astrant Implementation is in pre-launch verification and isn't open for purchase yet. Join the waitlist and we'll email you the moment it opens.

Join waitlist

Go Custom if you need any of these

The $1,299 Implementation tier works for about 80% of B2B SaaS sites. Consider Custom if:

→Complex public API with dozens of operations requiring tailored OpenAPI work
→Multi-region or multi-language content
→Bespoke MCP tools beyond the standard set (industry-specific capabilities, deep integrations)
→Major content rewrites across 20+ pages
→Multi-stakeholder approvals (your ops / legal / IT need a human liaison)
→Aggressive timeline constraints

See the Custom tier →

From payment to deployment

Step 1
Pay
$1,299 via Dodo Payments.
Step 2
Short questionnaire
Your site URL, what your three most important pages are, what your core service offerings are, and a delivery email for the patch. 5 questions, ~3 minutes. No repo URL needed — we don't touch your code.
Step 3
Pipeline runs
Automated build kicks off. You'll get progress updates by email as each stage completes.
Step 4
Delivery
Within 24 hours for standard sites. MCP server live, monitoring dashboard URL in your inbox, plus a Git-applicable patch file your developer applies with `git am` in about five minutes. You review the diff in your repo's normal workflow and merge when ready — no access to your repo or infrastructure required from us.

Everything we build, you own

No black box. Every artifact lives on your infrastructure. MCP server on your Cloudflare account. JSON-LD and content in your codebase via the patch your team applied. No dependency on Astrant for ongoing operation. You can cancel the subscription, move off our monitoring, or take everything in-house at any time.

FAQ

What if the automated build doesn't fit my stack?: The questionnaire catches common mismatches and steers you to Custom before you pay.
Which Git providers do you support?: All of them. We deliver a Git-applicable patch file that works for GitHub, GitLab, Bitbucket, Azure DevOps, and self-hosted Git. Your team applies it locally with `git am` and reviews via your normal PR workflow. We never need direct access to your repo.
Do you need write access to my repo?: No. The patch-file delivery model means we never touch your code directly. Many B2B security teams prefer this — fewer external service accounts with repo access is a security improvement, not a limitation. (If you're on the Custom tier and want us to open the PR for you, that can be arranged during the scoping call with a temporary deploy key.)

Ready?

Buy Implementation — $1,299