AI Chatbot for Kirby Sites

Bringing Dynamic Interaction to Flat-File Sites

Kirby's file-based architecture is one of its greatest strengths -- no database, no bloated admin panel, just content stored in text files and managed through an elegant panel or directly in your file system. Sites built with Kirby are fast, portable, and a pleasure to maintain. But flat-file simplicity also means there is no built-in way for visitors to interact with your site beyond reading what is on the page.

An AI chatbot adds a layer of dynamic interaction without compromising what makes Kirby appealing in the first place. The widget loads via a lightweight script, completely independent of your Kirby installation. It does not touch your content files, templates, or server configuration. Visitors get the ability to ask questions and receive immediate answers, while your site stays lean and database-free.

Ideal for Boutique and Portfolio Sites

Kirby is a favorite among designers, photographers, small studios, and independent professionals who need a site that reflects their craft. These sites often showcase work, explain services, and provide contact information -- but they rarely have dedicated support staff monitoring inquiries. A potential client looking at your portfolio at midnight has questions about your availability or process, and the contact form feels like shouting into a void.

A chatbot fills that gap instantly. Trained on your site's pages and any supplementary documents you provide, it can explain your services, describe your process, and point visitors to relevant examples of your work. The visitor gets the information they need to decide whether to reach out, and you get better-qualified inquiries when you check your inbox the next morning.

No Database, No Problem

Adding features to a Kirby site sometimes means writing custom plugins or extending templates with PHP snippets. But the chatbot requires none of that. You add a single script tag to your site's main template -- typically in the header snippet or footer snippet that Kirby loads on every page -- and the widget appears site-wide.

There is no Kirby plugin to install, no Composer package to require, and no panel field to configure. Everything about the chatbot -- its knowledge base, its appearance, its behavior rules -- is managed through the Asyntai dashboard, separate from your Kirby project. Your site's file structure stays as clean and organized as you built it.

Matching the Craftsmanship of a Kirby Build

Developers who choose Kirby over WordPress or a headless CMS are making a deliberate choice for simplicity, control, and quality. A chat widget on such a site needs to meet the same standard. If it looks generic or behaves clumsily, it undermines the care that went into the rest of the build.

The chatbot widget is fully customizable -- colors, border radius, fonts, placement, initial greeting, and suggested questions can all be configured to match your design language. On a carefully crafted Kirby site, the chat interface should feel like a natural extension of the design, not an external add-on.

Practical Support for Small Teams and Solo Builders

Kirby projects are typically built and maintained by one person or a very small team. That same person is often the designer, developer, content editor, and de facto customer support representative. When a visitor has a question about services, pricing, or project timelines, answering it manually means context-switching away from whatever else you were doing.

The chatbot absorbs the most common and repetitive portion of those inquiries. It works around the clock, answering questions based on your site content and uploaded materials. You spend less time responding to the same queries and more time on the creative and technical work that actually moves your projects forward. When a question requires your personal attention, the conversation logs make it easy to follow up on your own schedule.