# Solandra: full overview

> Solandra answers visitors from your website content, shows the source pages, and turns the questions it couldn't answer into a review list for your team. Plans from $39 a month, with a 7-day free trial.

Official site: https://solandra.io. Short index: https://solandra.io/llms.txt. This file is generated from the website's own pages and data, and covers public marketing information only.

## Overview

Solandra is in early access, built and operated by one person (the founder, based in India).

**How to get access.** Start a 7-day free trial: book a short call, walk the founder through your website and the questions you hear most, and your account is set up after the call.

It is for teams whose answers already live on a website, help centre or docs:

- **Product help:** Setup steps, feature questions, troubleshooting, and a list of the steps your guide explains badly.
- **Service information:** What a prospect wants to know before they book a call, answered from the pages you already wrote.
- **Policies and processes:** “How do I change my booking?” answered from the policy page, with the conditions you'd want them to see.

## What it does

### Answer visitors from your website

Connect a site, help center or docs and run a crawl. Visitors ask in their own words and get an answer built from your pages, with the sources attached.

- Website sources, crawled on demand.
- Answers grounded in your content, never invented from thin air.
- A Sources badge on every answer, linking to the pages it came from.
- Suggested questions to start the conversation.

### Find what your content is missing

Every question the assistant couldn't fully answer becomes a gap: the question, the count, the dates. Your team sees what visitors actually asked, not what you assumed they'd ask.

- Open and resolved gaps, grouped by question.
- The conversations behind each one.
- Resolve with a note for your team, then fix the content and crawl again.

A note saved on a gap is for your team; the assistant answers from your website, so the fix goes there.

### Hand off to a person when it matters

Visitors can ask for a human. The conversation escalates only when they confirm, your team gets an email, and whoever picks it up replies in the same chat with the full history in view.

- Escalation only on the visitor's request.
- Email to the people who handle support, straight away.
- Bubbles are labelled: visitors always know whether the assistant or your support team is speaking.

Your team provides the people and sets the hours. Solandra provides the handoff.

### Make it yours

Name, welcome message, suggested questions. Logo, brand colour, light or dark theme, corner style, launcher on the left or right.

- Preview the real chatbot in the dashboard before it goes live.
- Paste one script tag on your site.
- Change a setting later and every page picks it up.

### Keep knowledge where it belongs

One project per knowledge base; several chatbots on the same project when the same content needs different names or introductions. Sources marked private never reach a public chatbot.

## Sources and supported content

**What you can connect.** Website pages Solandra's crawler can reach, PDF files you upload, and answers you write yourself. Other connectors aren't available yet.

Website pages are read by a crawl that you start from the dashboard. Pages marked private never reach a public chatbot; internal chatbots can use both public and private sources. Pages, re-crawls and pages read a month are limited per plan (see Pricing).

## Chatbots, conversations, gaps and handoff

- Chatbots: a public chatbot sits on your website with one script tag; an internal chatbot is for your team and can also answer from private sources. Both count towards the plan's chatbot limit.
- Conversations: your team sees the full thread and replies in the same chat. If the visitor left an email address when they asked for a person, the reply is also emailed with a link back to the conversation.
- Gaps: every question the assistant couldn't fully answer is listed with its count and dates. After a fix, the question is asked again through the assistant before the gap is marked resolved. Resolving with a note is for your team: the assistant answers from your website content, so the fix goes there.
- Human handoff: the conversation escalates only when the visitor asks and confirms; your team is emailed.

## Pricing

Prices are in US dollars; tax is added at checkout where it applies. Payments are processed by Dodo Payments as merchant of record. The [pricing page](https://solandra.io/pricing) is the source for current limits.

### Starter: $39 a month

One website and a small team getting started. Or $390 for your first year, billed yearly.

**Knowledge**
- 1,000 pages
- Manual re-crawl, 1 a day

**Answers**
- 4,000 AI replies a month
- 200 Gap fix checks a day

**Team**
- 2 seats
- 1 project
- 2 chatbots, public or internal

### Growth: $149 a month

A busy site, or a few sites, with a support team. Or $1,490 for your first year, billed yearly.

**Knowledge**
- 10,000 pages
- Automatic re-crawl (coming soon)
- Manual re-crawl, 2 a day

**Answers**
- 12,000 AI replies a month
- 500 Gap fix checks a day

**Team**
- 5 seats
- 3 projects
- 6 chatbots, public or internal

### Scale: $399 a month

Large sites, several products and a whole support team. Or $3,990 for your first year, billed yearly.

**Knowledge**
- 50,000 pages
- Automatic re-crawl (coming soon)
- Manual re-crawl, 5 a day

**Answers**
- 40,000 AI replies a month
- 1,000 Gap fix checks a day

**Team**
- Unlimited seats
- 10 projects
- 20 chatbots, public or internal

### Compare plans

| Limit | Starter | Growth | Scale |
| --- | --- | --- | --- |
| Pages (What your chatbots can answer from) | 1,000 | 10,000 | 50,000 |
| Pages read a month (Crawling and re-crawling your sites) | 2,000 | 20,000 | 100,000 |
| Manual re-crawls a day | 1 | 2 | 5 |
| Automatic re-crawl | No | Coming soon | Coming soon |
| AI replies a month | 4,000 | 12,000 | 40,000 |
| Gap fix checks a day (Each project; re-asking a fixed question to confirm the fix works) | 200 | 500 | 1,000 |
| Seats | 2 | 5 | Unlimited |
| Projects (A knowledge base each) | 1 | 3 | 10 |
| Chatbots (Public on your site, or internal for your team) | 2 | 6 | 20 |
| Questions a day, each chatbot (A safety cap against abuse) | 2,000 | 3,000 | 5,000 |
| Going over on monthly plans | Yes | Yes | Yes |

### What the limits mean

- **Pages:** One normal web page or document section, about 400–500 words. A short page counts as one; a very long page can count as two or three. It's what's indexed right now, so crawling again doesn't use more.
- **Manual re-crawl:** When your site changes, start a re-crawl from its Source in the dashboard. We read the site again and update what changed. The number is how many you can start a day, across your projects.
- **Automatic re-crawl:** Coming soon. We'll watch your sitemap.xml and re-read only the pages whose last-modified date changed, so your chatbots stay current on their own. If your sitemap isn't kept up to date, you can still re-crawl by hand.
- **Pages read a month:** Each page we fetch while crawling or re-crawling counts once, changed or not. A full re-crawl of a 1,000-page site reads 1,000.
- **AI replies:** Every time the assistant answers someone: a real answer, small talk, or offering to connect them to a person. A question it couldn't answer doesn't count; it shows up in Gaps instead.
- **Gap fix checks:** When you fix a Gap, we ask the assistant the question again to confirm the fix works before marking it resolved. Each re-ask is one check, counted per project.
- **Seats:** One person on your team, you included. Someone in several projects counts once.
- **Projects:** One knowledge base with its own Sources, chatbots, Gaps and team. Use one for each website or product.
- **Chatbots:** A public chatbot sits on your website for visitors; an internal one is for your team and can answer from private sources too. Both count, across all your projects.
- **Questions a day, each chatbot:** A safety cap against abuse: the most questions one chatbot takes in a day. Normal use stays well under it.

### Included in every plan

- A chatbot on your website, with sources on every answer
- An internal chatbot for your team, answering from private sources too
- The dashboard your team uses day to day
- Gaps: every question the assistant couldn't answer, listed and easy to fix, then re-checked through the assistant before it's marked resolved
- Handing off to a real person when a visitor asks for one

### If you go over

- +1,000 pages: $20 / month
- +1,000 AI replies: $7 / month
- +1 seat: $7 / month

No surprise jump to a bigger plan: going over adds a small, predictable amount to that month's bill. We email you at 80% and 100% of your plan, and if usage reaches twice your plan the assistant pauses and we email you, so a fault can't run up the bill.

Yearly plans don't go over: usage stops at the plan, and you can upgrade any time. Projects and chatbots are fixed per plan.

### Offers and trial

- Launch offer: 20% off your first 3 months on a monthly plan.
- Pay yearly: 2 months free in your first year.
- One offer per subscription. The launch offer applies to monthly plans; the yearly offer to your first year, which then renews at 12 months' price.
- Free trial: A trial lasts 7 days on your own content and costs nothing. No card is needed, and nothing is charged when it ends.

### Cancelling and refunds (from the [refund and cancellation policy](https://solandra.io/refund-policy))

**Cancelling.** You can cancel at any time. Cancelling stops the next renewal: your plan keeps working until the end of the period you've paid for, and nothing more is charged after that. To cancel, email [contact@solandra.io](mailto:contact@solandra.io) from your account's email address, or use the billing page in your dashboard once it's available.

**Refunds.**

- **Within 7 days of your first payment:** a full refund, for a monthly or a yearly plan. Ask by email within 7 days of that payment; the subscription ends when the refund is made.
- **After that:** payments aren't refunded, including for part of a month or the unused part of a year. You keep access until the end of the paid period.
- **Overage:** charges for pages, AI replies or seats already used aren't refunded.
- **Billing mistakes:** a duplicate charge or a charge we made in error is always refunded in full.

The 7-day refund applies to the first payment of your first subscription. Nothing here limits a right you have under the law where you live.

## Current limitations

- **Can the AI be wrong?** Yes. It answers from your content and says when it can't, but it can still miss or misread something. The source links and your team's review are there for the details that matter.
- **What can I connect?** Website pages Solandra's crawler can reach, PDF files you upload, and answers you write yourself. Other connectors aren't available yet.
- **Does it update when my website changes?** Run a new crawl after you publish changes. Updates aren't continuous yet.
- **What it doesn't do.** The assistant explains your content. It doesn't look up a visitor's account, change an order or act in another system.
- **Coming soon, not available yet:** Automatic re-crawl (Growth and Scale).
- **Yearly plans** don't go over: usage stops at the plan. Monthly plans can go over, up to twice the plan.

### AI answers (from the [terms of use](https://solandra.io/terms-of-use))

Answers are generated by AI from your content. They can be incomplete, outdated or wrong. Source links show what was retrieved, not that every sentence is correct. Review answers that matter, keep your content current, and do not rely on Solandra alone for medical, legal, financial or safety decisions.

Marking a gap as resolved records your team's action. It does not teach the assistant anything; the content has to contain the answer.

## Security and data handling

The authoritative texts are the [data security](https://solandra.io/data-security), [privacy policy](https://solandra.io/privacy-policy) and [subprocessors](https://solandra.io/subprocessors) pages. Their content follows.

### Data security page

Solandra processes the content you connect and the conversations people have with your assistant. These are the controls and boundaries to understand before using it.

#### Project access and roles

Dashboard access requires sign-in. Protected service requests verify the session and check project membership. Roles control who can manage sources and widgets, review gaps, assign team access, and delete resources.

Knowledge retrieval is scoped to a project. Separate projects are the way to keep distinct knowledge bases apart.

#### Public and private source visibility

Public widgets retrieve from sources marked public. Private sources are excluded from public answers; authenticated internal requests can use both public and private sources when authorized for the project.

All public widgets in one project share its public source set. Making a source private does not protect its original website URL or retract content already shared in an earlier conversation.

#### Authentication and browser protections

Solandra uses Supabase Auth for account authentication. The dashboard stores its access token in an HTTP-only cookie so browser scripts cannot read that cookie through the normal document-cookie interface.

The dashboard includes browser headers that prevent framing and restrict selected browser capabilities. Public widgets support an allowed-origin setting that restricts where browsers can embed the widget when configured.

The public widget key identifies an assistant; it is not a secret or proof of a visitor's identity. An embedding restriction does not make a public assistant or its API private.

#### Controls around requests and AI input

The service applies request limits and daily widget caps to help limit abuse and excessive use. Selected sensitive fields are redacted from application logs.

Answer generation is instructed to use retrieved source content and to identify insufficient evidence. Retrieved page text is treated as reference material rather than trusted instructions. These measures reduce some risks; they do not guarantee perfect answers or eliminate every prompt-based attack.

#### Service providers and AI processing

Operating the assistant involves providers for crawling, authentication, storage, AI, hosting, and email. Relevant source text, questions, and conversation context may be sent to the AI provider. Private source visibility does not prevent service-provider processing.

[Review subprocessors and processing locations](https://solandra.io/subprocessors)

#### Hosting and operational safeguards

Solandra runs on managed providers, each with its own security programme: Supabase (Pro plan) for authentication and the database, Qdrant Cloud for the search index, Railway for the applications, Resend for email and OpenAI for AI. All traffic uses HTTPS. Data is encrypted at rest by those providers. The database is backed up daily by Supabase. Administrative access to every provider is held by the founder alone and protected with two-factor authentication. Application logs redact tokens and secrets. Security reports go to [contact@solandra.io](mailto:contact@solandra.io) and are answered by the founder directly.

#### Your team's part

- Connect content you are authorized to use and review what is marked public.
- Give project access only to the people who need it.
- Keep passwords and API secrets out of website content and conversations.
- Check important answers against the underlying sources.
- Contact us before using the service for information with special handling requirements.

#### Data removal and retention

Pausing or making a source private affects its use in answers after the change is applied. It does not erase earlier conversations. Starting a new conversation changes the visitor's current conversation; it is not a deletion request.

Retention and deletion practices are described in the [Privacy policy](https://solandra.io/privacy-policy). Contact [contact@solandra.io](mailto:contact@solandra.io) for a data request.

#### Report a security issue

Email [contact@solandra.io](mailto:contact@solandra.io) with a description of the issue and the smallest set of steps needed to understand it. Please avoid accessing, changing, or including another person's data in a report.

If you have specific security requirements, [talk with the founder](https://cal.com/yrjdev/solandra) before connecting content.

### How long data is kept (from the privacy policy)

- **Account information:** 30 days after the account is closed, then deleted.
- **Connected content and its index:** deleted when you delete the source, and in any case 30 days after account closure.
- **Conversations, gaps and escalations:** 12 months, or earlier if you delete the project. We will announce any change to this.
- **Logs:** up to 30 days.
- **Backups:** the database is backed up daily by Supabase; a deleted record can persist in a backup for up to 30 days before it expires.
- **Billing records:** as long as tax and accounting law requires.
- **Correspondence:** while we are in contact, and up to 24 months afterwards.

### Subprocessors

**Last updated:** 20 October 2026

These are the providers that process data to run Solandra. Each receives only what its job needs and is bound by its own data processing terms. Existing customers are emailed before a new provider starts handling their data. How we use this data is in our [privacy policy](https://solandra.io/privacy-policy).

| Provider | Job | Location |
| --- | --- | --- |
| Supabase | Authentication and the database | India |
| Qdrant Cloud | Search index of your content | Ireland |
| OpenAI | AI routing, embeddings and answers | United States |
| Resend | Emails to your team, and to visitors who left an address for a reply | Ireland |
| Railway | Running the dashboard, widget, API, workers and the crawler that fetches the website pages you connect | Singapore |
| Dodo Payments | Subscriptions, payments, tax and invoices, as merchant of record | As described in [Dodo's privacy policy](https://dodopayments.com/privacy-policy) |
| Google Analytics | Measuring visits to this website (solandra.io only) | United States |
| Cal.com | Booking a meeting with the founder | United States |

Need more detail for a security review or a data processing agreement? Email [contact@solandra.io](mailto:contact@solandra.io).

## Pages

- [Home](https://solandra.io/)
- [What Solandra does](https://solandra.io/services)
- [Pricing](https://solandra.io/pricing)
- [About](https://solandra.io/about)
- [Contact](https://solandra.io/contact)
- [Data security](https://solandra.io/data-security)
- [Privacy policy](https://solandra.io/privacy-policy)
- [Terms of use](https://solandra.io/terms-of-use)
- [Refund policy](https://solandra.io/refund-policy)
- [Subprocessors](https://solandra.io/subprocessors)

## Contact

- Book a meeting with the founder: https://cal.com/yrjdev/solandra
- Email (support, privacy and security reports): contact@solandra.io