AI Chatbot for Astro Sites

You chose a framework that ships almost no JavaScript. A support widget that undoes that is not an option, which is why this one is a single deferred script that loads after the page is already usable.

Get Started Free See Pricing

Try it on your own site for free

Enter your Astro site URL and see how an AI assistant would answer your visitors

See It In Action

For content sites, docs and marketing pages built with Astro

AI assistant on a performance-focused Astro site

Respects the Zero-JavaScript Default

Astro ships static HTML by design, and every kilobyte of client JavaScript is a deliberate decision. The assistant is one deferred script under 50KB that loads after your content, so your performance profile stays intact.

Adding the Asyntai script tag to an Astro layout

One Tag in Your Layout

No integration to install, no island to hydrate, no framework component. A script tag in your base layout applies to every page Astro builds.

AI answering documentation questions

Answers Documentation Questions

Readers arrive at docs with a specific problem and rarely find the exact page. The assistant answers from your published content, which is faster than any search box.

AI reading published pages rather than source content

Survives a Content Rebuild

Because it reads your published pages rather than your content collections, restructuring markdown or changing your content schema does not affect it.

Chatbot answering visitors in several languages

Thirty-Six Languages

Detected per visitor, with no i18n routing work on your side.

Have any questions? Try our AI chatbot right now

Ask it anything - it is live on this page

Built for Astro Merchants

One script tag in your layout. No integration, no hydration.

Under 50KB, Deferred

Loads after the page is usable, so Lighthouse scores and Core Web Vitals stay where you put them.

No Integration to Install

A plain tag, so nothing enters your astro.config or your dependency tree.

Answers From Published Pages

It crawls the built site, which keeps it independent of your content collections and schema.

36 Languages

Detected per visitor without i18n routing changes.

Collects Enquiries

Ask for what you need before handing over a lead or a support request.

No Invented Documentation

It answers from your content and says when something is not covered.

Simple Astro Integration

One script tag in your base layout covers every page. Nothing is added to your config or dependencies.

  1. 1

    Sign up and copy your snippet

    Create your Asyntai account, add your site URL so the AI can read your published pages, then copy the snippet from your dashboard.

  2. 2

    Open your base layout

    Add the tag before the closing body tag in the layout your pages extend.

  3. 3

    Build and deploy

    The tag ships with your static output; no hydration or client directive is required.

  4. 4

    Configure from the dashboard

    Tone, rules, uploaded documents and appearance live outside your repository.

Get Your JavaScript Snippet

Sign up free and get your personalised snippet instantly - paste it once and the widget is live

Why Astro Developers Choose Asyntai

Start free with 100 messages, upgrade as traffic grows

No Performance Regression

A deferred sub-50KB script does not undo the reason you chose Astro.

No Dependency Added

Nothing in package.json, nothing in the config, nothing to upgrade.

Readers Get Answers Faster Than Search

Conversational answers beat a search box for anyone who cannot guess your terminology.

Ready to add an AI assistant to your Astro site?

Start free with 100 messages. No credit card required.

Create Free Account

Frequently Asked Questions

What Astro developers ask first

How do I add it to an Astro site?
Put one script tag in your base layout before the closing body tag. There is no integration to install and no client directive needed.
Will it hurt my Lighthouse score?
It is under 50KB and deferred, loading after your content is interactive, so it does not block rendering or affect Core Web Vitals meaningfully.
Does it need hydration or an island?
No. It is plain JavaScript loaded at runtime, entirely outside Astro’s component model.
Where does its knowledge come from?
Your built and published pages, crawled on demand, plus uploads for anything not published.
Does restructuring content break it?
No. It reads the rendered site rather than your content collections, so schema and folder changes are invisible to it.
Can I limit it to some pages?
Yes. Put the tag in a specific layout rather than the base one if you only want it on, say, the docs section.
Which languages does it support?
Thirty-six, detected from what each visitor writes.
What happens at the message limit?
Free includes 100 messages a month, Starter 2,500. At the limit it pauses until the next reset, or you upgrade instantly.
Can I use it on several sites?
Yes, each with its own knowledge base. Free covers 1, Starter 2, Standard 3, and Pro up to 20.

What an AI Assistant Adds to a Static Site

Performance Discipline Rules Out Most Widgets

Teams that choose Astro have usually been burned by JavaScript bloat and are deliberate about what runs in the browser. Most support widgets fail that test immediately: heavy bundles, render-blocking loads, layout shift.

A single deferred script under 50KB is a different proposition. It arrives after the page is usable and does not compete with your content for the main thread, which makes it defensible in a codebase where weight is reviewed.

Docs Are Where Search Fails Hardest

Documentation search only works for readers who already know the vocabulary. Everyone else searches for the problem in their own words, gets nothing useful, and leaves with the impression that the docs are incomplete.

Answering conversationally from the same pages fixes the access problem rather than the content. Readers describe their situation and get pointed at the right page, which is what they wanted from search.

Reading the Built Site Beats Reading the Source

Integrations that parse content collections or markdown frontmatter break whenever the content structure changes, and content structure changes constantly on active sites.

Crawling the rendered output avoids that entirely. Whatever your source looks like, the published pages are the contract with your readers, and that is what the assistant reads.

Static Sites Still Get Sales Questions

Marketing sites built with Astro are often the front door to a product, and visitors ask commercial questions the page deliberately leaves out: pricing edge cases, integrations, whether it fits their scale.

Answering those without adding another section to the page keeps the page fast and focused while still converting the visitor who needed one more fact.

Nothing to Maintain in the Repo

Every dependency added to a static site is a future upgrade, an audit item and a potential build failure. Keeping the repository clean is part of why the stack was chosen.

A script tag introduces none of that. Configuration lives outside the project, and removing it is deleting one line from a layout.

Ready to Add Support Without Adding JavaScript Weight?

Start free with 100 messages and keep your build exactly as light as it is.

Start Free - No Credit Card Required