Questions

Minutes. Name the bot, give it your website address, let it find your pages, press Teach, then paste one line into your site. All of it happens in a browser.

Only for the last step, and only if you can't edit your own pages. The install is a single <script> tag; there is no SDK, no build step and nothing to host.

Yes, and on anything else that lets you paste a script tag into your page. There is no plugin and nothing specific to your platform: the install is one <script> line, so it goes wherever your builder keeps custom code — Squarespace's code injection, a WordPress theme footer or custom HTML block, Wix's custom code, a Shopify theme layout. Put it site-wide and the bot is on every page; put it in an embed block on one page and it is on that page.

Pages from your own site, which it finds by crawling from the address you give it, plus any .txt or .md documents you upload: a price list, an FAQ, a policy. You can add and remove individual pages by hand, and the bot only ever uses what is in that list.

That is fine, and common. Your bot works from about a dozen sources rather than your whole site, so the job is picking the right ones, not collecting everything. Add the pages visitors actually ask about — what you do, what it costs, where you are, when you are open, the one policy people always query — and drop anything the crawl found that isn't earning its place. For anything that isn't on a page at all, upload a .txt or .md. If your business genuinely needs more than that, email help@ludonode.com and we will talk about a custom solution.

Yes, but it only knows what you give it: a four-page site makes a four-page bot. The crawl can only find what is already written down, so this is what the uploads are for. Put your prices, your hours, your services and the questions you answer on the phone all day into a .txt or .md and hand it over. Most of what a visitor wants to know is something you know by heart and have never put on the site.

No, and deliberately. Crawling and teaching are both buttons you press, so nothing changes what your bot says without you deciding it should. Just tell the bot to update whenever your content changes.

Yes. Teaching produces one reference summary out of every page and document, and you can read the whole thing back before anyone else talks to it. There is a Preview page for trying the real widget before you publish it.

It says so. Prices, hours and policies are quoted from your material exactly as you wrote them, and where your site covers nothing it tells the visitor that rather than inventing an answer.

That is the one thing it does besides answer. When a visitor asks for a person, wants a callback, or raises something your pages don't cover, the bot takes their message and their email or phone and puts it in your inbox, flagged if they asked for a reply.

No. There is a cap on how many messages one visitor can leave in a day. When somebody reaches it the bot carries on talking to them normally, tells them their earlier messages have been passed on, and points them at your own contact details for anything further.

Not in their words, and that is deliberate. Anything a visitor deliberately sends you arrives in your inbox in full. Everything else is counts — how many chats, how many messages, how long people stayed — because conversations expire within hours and nothing anyone typed is kept for analytics. Nobody gets a searchable log of your widget, us included.

Whichever one the visitor writes in. There is no setting and nothing to configure per language.

Its name, one of four personalities (professional, friendly, concise or verbose), your brand color, the text in the empty composer, and up to three one-tap opening questions. None of it is locked in; change it and the bot changes.

Ours by default, included in the plan with nothing to set up. Or connect your own provider key from Claude, OpenAI, Gemini, Grok, Groq, DeepSeek, Azure, DigitalOcean, Fireworks or a local Ollama, and pick the exact model. The prompt allowance is the same either way, and your own key means your own rates.

Yes, and every bot has one. It is a REST API with keys of its own: ask the bot a question, read and add sources, start a learning run, pull usage and analytics. Professional and Commerce run it for real. On Free and Local it is a test drive — the whole API, every endpoint, on your own bot, capped at ten calls a day with reads counting toward the ten. Build the integration, watch it answer, then move up: the cap lifts and it is the same key and the same code, with nothing rewritten.

It is a server-side API, deliberately. There are no CORS headers on it, because a key in a page's JavaScript is a key handed to everyone who loads the page. The widget is the thing that belongs on a web page.

Only if you let it. There is a switch that restricts the bot to your own domain and its subdomains; it is off while you are testing, because a staging copy lives somewhere else.

One website. It has its own sources, its own name, its own personality and its own branding. Two websites means two bots.

One thing a visitor asks, and the answer they get back. If somebody asks four things in one conversation, that is four prompts.

Local answers up to 1,000 a month, Professional up to 3,000, Commerce up to 15,000. It is a ceiling, not a meter: you are not billed per prompt, and nothing costs extra until you reach it.

Free, if you have not seen it working on your own pages yet — it is the same bot, and the work you do setting it up carries over when you pick a plan. Otherwise the one that sounds like your business. Local suits a restaurant, a trade or a single shop; Professional suits a practice, a firm or an agency; Commerce suits an online store or anywhere the traffic is heavy. It is the same bot in all three — what changes is how many prompts it will answer, and Professional lifts the daily cap off the API and adds priority support. Moving up later takes a minute and nothing is rebuilt.

Yes — start a free bot and point it at your own site. It reads your pages, answers from them, and takes messages, and you can talk to it in your admin panel for as long as you like. The one thing it will not do is go on your website; that is what a paid plan adds. No card, and nothing to cancel.

The API comes with it on the same terms: ten calls a day across every endpoint, enough to build an integration and see it working before anybody is charged for it. Local includes the same test, and Professional is where the daily cap comes off.

The bot on the home page is the same product, pointed at our pages instead of yours.

Yes, and it takes effect the moment you confirm it. You pay the difference rather than the whole new price: what you have already paid for the rest of this period is credited against the new rate, so the charge today covers only the days left in it. The larger prompt allowance is there straight away, and nothing else moves — same bot, same sources, same script tag on your site.

Yes, and it takes effect at your next renewal date. Nothing is taken away early: you keep the plan you paid for until the period you paid for ends, and the smaller rate starts from that date. There is nothing to pay on the day you ask, the change sits on your plan page until then, and one button keeps your current plan if you change your mind. Switching from yearly billing to monthly works the same way and waits for the same date.

The bot keeps running and keeps answering until the end of the period you already paid for. After that it goes dormant and tells visitors it is unavailable. Nothing is deleted, and resuming brings it back with its sources intact.

No. Teammates are free. Billing is per bot, so inviting the rest of your team costs nothing, and you choose which bots each of them can reach.

Where your bots live and who can reach them. You get one when you sign up, it holds your bots, your teammates and your billing, and for most people that is the whole of it — one team, one bot, nothing to think about. It matters when there is more than one of you, or more than one client: a second team is a clean wall between two sets of bots. Teams cost nothing, and so do the people you invite into them.

Yes, one grant at a time: reading the dashboard, reading the inbox, deleting from it, configuring the bot, billing, and inviting people are all separate. So somebody can work your inbox all week without being able to change a word the bot says. Grants are held per team, which with one team and one bot is the same as per bot. Whoever created the team owns it and keeps that.

Yes, and teams are built for it. Each client gets a team of their own with only their bots in it, and you invite their people into that team rather than into yours. Nothing crosses between teams: a bot, its inbox and its analytics are visible only inside the one that owns it. Billing stays per bot and sits on the team, not on you, so each client can carry their own — or you can hold it yourself and bill them your way.

Email help@ludonode.com and we will sort it out. We would rather refund you than argue with you.

At its own address on our servers, with its own isolated dataset, encrypted on disk. It has no idea what else you own and no way to look up anything about anyone else's.

Hours, not forever. A chat session expires on its own, and what is left behind is counters: how many chats, how many messages, how long people stayed. Nothing a visitor typed is retained for analytics.

Your bot's data is encrypted on disk, and everything between a visitor and the bot travels over TLS.

No. Your pages and documents are the reference material your own bot answers from, and nothing else.