Auto Secure LoginPlatform
LiveWebApiApplianceAndroidAI you can own

An answer desk that never makes things up

Answers your customers only from your own approved content, cites every claim, and runs on hardware you own.

Built for: A support lead who answers the same twenty questions every week and wants them answered once, correctly, with the policy attached · An owner or operations manager whose published policies, manuals, and price lists are the real product knowledge, and who cannot risk a confident wrong answer · A compliance or records person who needs to show what was published, when, from which source, and every time the assistant declined to answer · An IT or security lead who has been told to add AI to the website but will not send company material to an outside AI service

$0.00Outside AI spend per answer, measured on a live instance on 2026-08-25
46 MBMemory the running assistant used on that same live instance
804 KBAll content and records for every tenant on that same instance
7Findings raised by the pre-launch security review, all fixed and re-verified against the live service before launch

The problem

Viavitna exists because of this.

You have written it all down already. The returns policy, the eligibility rules, the setup steps, the hours, the fee schedule. It is on your website, in your handbook, in a document somebody made three years ago. And still the same questions arrive every single day, and somebody on your team stops what they are doing and types the answer again. So you look at adding AI to the website. And then you actually test one. You ask it a question your policy answers plainly, and it answers beautifully, and every so often it answers beautifully and wrong. It invents a thirty-day window when yours is fourteen. It states a fee that does not exist. It sounds more certain about the made-up answer than the real one, because sounding certain is what it was built to do. There is no source to click, so your customer has no way to catch it and neither do you. The first time you find out is when somebody quotes it back at you and expects you to honour it. The second problem arrives right behind the first. To make the assistant work, you have to hand your material to somebody else's AI service, and then hand them your customers' questions too. Every question a visitor types is a question about your business, leaving your building. Meanwhile the bill is a meter: the more useful it gets, the more it costs, and the vendor has a quiet incentive for it to keep talking rather than admit it does not know. You end up choosing between a chatbot you cannot trust and no chatbot at all, and most people pick no chatbot at all.

What changes

  • You own it. The engine, the AI models, and your content sit on a machine inside your network, on a disk your licence key unlocks. That is the default way it is sold, not an enterprise upsell.
  • No outside AI service is in the answer path in any configuration, so your content and your customers' questions never leave your control and there is no third-party AI bill to pass on.
  • Unsupported claims are deleted before the answer reaches a visitor, by two independent checks. If the semantic check cannot run at all, the entire written answer is thrown away rather than shipped.
  • It abstains on purpose. Most assistants in this category are tuned to keep the conversation going; this one is tuned to stop.
  • Never metered per question. Charging for questions would reward an assistant for talking, and this one is supposed to know when to be quiet.
  • Reproducible answers — zero temperature, fixed seed, constrained output — so you can test it, review it, and sign off on it the way you would sign off on a document.
  • A draft you can interrogate before anything is public, with hash-verified version history and recovery back into review that never publishes by itself.

What it does

How Viavitna works, start to finish.

Viavitna is a question box that answers only from content you have approved, shows the source behind every sentence, and stays quiet when your material does not cover the question. You load your pages, policies, and FAQs. It reads them and nothing else. A general-purpose model does the writing, but it is never allowed to contribute a sentence that your own text does not support, because filling in gaps is the failure you are trying to avoid. The way it gets that guarantee is worth understanding, because it is the whole product. When a question comes in, Viavitna finds the passages of your content that bear on it, then drafts a short answer where every claim points at a specific passage. Then it checks its own work with two independent checks. The first is mechanical: does this claim actually cite a passage, and does every number, date, price, and link in it appear in that passage? If not, the claim is deleted. The second reads the passage and the claim side by side and asks whether the passage really supports the claim and whether the claim really answers the question. If that second check cannot run, or comes back malformed or incomplete, nothing generated is accepted at all. The answer you see is composed only of the claims that survived. The writing part proposes; the checking part decides. When nothing survives, Viavitna does not improvise. It falls back to showing the relevant passage from your own content, quoted and cited, or it says plainly that the published material does not cover this. That same floor catches every kind of failure: the question is off-topic, the content genuinely does not answer it, or the model is unavailable. Every one of those produces a plainer answer, never a guess. Unsafe requests, attempts to fish for a credential, and requests to look up somebody's account are refused before any of this starts. Nothing you upload goes live by accident. An upload becomes a private draft. You sit with it, ask it the ten questions your team actually hears, read the citations, and decide. Only then do you publish. Every earlier draft is copied, hash-checked, and kept, and can be brought back into review, so a bad edit is never a one-way door. Once published, adding it to your website is one line, and your own systems can query it directly. The part that makes Viavitna different from everything else in this category is where it lives. This is not a service you rent access to with a self-hosted option bolted on the side. The normal way to buy Viavitna is to own it: the engine, the AI models, and your content all sit on a machine inside your own network, on an encrypted disk that your licence key unlocks, and nothing about your business or your visitors' questions ever leaves the building. There is no outside AI service in the answer path in any configuration, which is also why there is no per-question bill. We do operate a managed version for people who genuinely cannot run their own machine, and we will tell you plainly that it is the lesser choice, because it is the only setup where your content sits somewhere other than with you.

Features

Everything in the current release.

Each of these is built and working today. Nothing on this list is a roadmap item.

01

It only knows what you gave it

Viavitna answers from the pages, policies, and FAQs you loaded, and from nothing else. A general-purpose model does the writing, but a claim it cannot tie to one of your passages is deleted before you ever see it. If your handbook does not say it, the assistant cannot say it either.

02

Every answer shows its source

Each answer arrives with a link to the exact page and section it came from. Your visitor can click through and read the original for themselves, which means a wrong answer is catchable in one click instead of six months later. Your own team gets the same handle when they audit what the assistant has been telling people.

03

It says it does not know

When your content does not cover a question, Viavitna says so in plain language rather than producing something that sounds right. Ask it something your site has never addressed and it declines. This is the behaviour your attorney prefers over a confident guess, and it is the default, not a setting you have to find.

04

Two independent checks before anything reaches a visitor

Every claim is checked mechanically for whether it cites real source text and whether its numbers, dates, prices, and links actually appear there. A separate check then reads the source and the claim together and decides whether the source truly supports it and whether it answers the question asked. Claims that fail either check are deleted, and if the second check is unavailable, malformed, or incomplete, the whole written answer is rejected and the plainer floor answers instead.

05

Nothing goes live until you say so, and every version stays recoverable

Uploading content creates a private draft that visitors cannot reach. You interrogate it with real questions, read the citations, fix your content, and re-upload as many times as you like; publishing is a separate, deliberate act. Every earlier version is copied, hash-verified, and kept rather than overwritten, and you can restore one back into review at any time. Restoring never publishes anything by itself, so recovering from a bad edit cannot accidentally push it live.

06

Content goes in as it already exists

Web pages, HTML, Markdown, and plain text go in as they are, with no re-tagging and no rewriting. We can also crawl your live site to build the first draft for you, rendering the pages so that text your site loads in the browser is captured rather than missed. Material that lives in another format — a document or a scanned file — has to be converted to text before it can be loaded, which is part of what the no-charge content-fit review sorts out.

07

The same question gives the same answer

Viavitna is built to be reproducible rather than random: the writing step runs at zero temperature with a fixed seed and a constrained output shape. Ask it the same question against the same published content and the same model and you get the same answer, which is what makes it something you can test, review, and sign off on. It behaves like a system with rules rather than a slot machine.

08

When the clever part breaks, it gets plainer, not wrong

If the writing model is unavailable for any reason, Viavitna keeps answering by quoting the relevant passage of your content directly, still cited. Visitors see a plainer answer rather than an error page, and never a guess. Availability is allowed to degrade; truthfulness is not.

09

The questions your content could not answer, ranked

Viavitna keeps a tally of the questions it had to decline, most-asked first, without ever storing the words a visitor typed. What you get is how many distinct questions went unanswered, how often each one came back, in which language, and which of your sources came closest — enough to point at the gap in your content, deliberately not enough to read anybody's message. It is pulled as a report rather than shown as a live dashboard.

10

A record behind every answer, and a compliance record for any period

Each completed answer carries a tamper-evident receipt binding which version of your content was serving, which passages were used, and what the verification decided, so if somebody later asks why the assistant said what it said, you can show them. For any period you choose, a report can be pulled covering what was published and when, which sources it came from, how many questions arrived, and every single time the assistant declined to answer. Regulated buyers press hardest on those declines, so the abstention record is a first-class part of it, produced without retaining any visitor's words. The receipt proves what the system decided, not that your source material was itself correct.

11

It tells you when your published pages have moved on

The one genuinely dangerous failure for a cited assistant is a confident answer pointing at a page that has since changed. A scheduled check re-fetches the live pages behind your content, compares them to what it was given, and reports drift — with changed figures, times, and prices weighted hardest, since those are the answers people act on. Where a page cannot be checked honestly, it says so rather than raising a false alarm. It never republishes on its own, because changed content deserves the same human review the first upload got.

12

Runs sealed on your own hardware

The owned version ships as a self-contained image you run on a machine you control, with the AI models included and the disk encrypted end to end. The licence key we issue is what unlocks it, and without that key the whole thing — models, engine, and your content — is unreadable. It needs no inbound access and installs nothing on your existing systems; it runs as its own sealed machine on hardware you already have.

13

Your visitors' questions are never written down

Viavitna does not store the words in a question, and there is no setting anywhere that turns that back on. The short operational record keeps a scrambled fingerprint, the character count, the language, the outcome, which sources were used, and how long it took, so you can measure coverage without reading what people typed. It is kept 30 days by default, and older records that predate the rule are stripped rather than grandfathered.

14

English, Spanish, and Chinese from your own content

A visitor gets an answer in the language they typed in, drawn from the material you published in that language. The question's own language wins over whichever version of the page they happened to land on, so a bilingual visitor typing in Spanish on an English page is not forced into the wrong one. The question box is built for keyboard operation throughout: it announces new answers to a screen reader, labels its controls, closes on Escape and returns focus, and draws a visible focus outline.

15

One line on your site, plus a direct connection and a phone client

Adding Viavitna to your website is a single line pasted once, with no build tooling and no development work. The key in that line is publishable by design and is protected by a per-visitor rate limit; at setup we also restrict it to your own domains, so a copied key stops working elsewhere. Your own systems can query the same assistant directly for custom screens or workflows, and there is a finished native Android client for staff away from a desk — built and signed, though not yet published to Google Play.

Proof

Numbers we can stand behind.

Every figure below comes from the product's own release record or test suite, not from a marketing estimate.

$0.00Outside AI spend per answer, measured on a live instance on 2026-08-25
46 MBMemory the running assistant used on that same live instance
804 KBAll content and records for every tenant on that same instance
7Findings raised by the pre-launch security review, all fixed and re-verified against the live service before launch
186 filesEvery file in the live release hash-verified against the exact source revision it names
0Regressions permitted by the frozen answer-quality gate before any model change ships
23Locked must-answer and must-refuse cases in the hash-frozen set, run nightly and required before a model change
3 languagesEnglish, Spanish, and Chinese are required slices of that gate, answered from the customer's own material
  • A per-answer receipt and a period record that includes every declined question, not just the successful ones.
  • It reports when your live pages have drifted away from what it was given, which is the one failure a cited assistant cannot otherwise detect.
  • Question wording is never stored, and there is no configuration option that can enable it — including for records written before the rule existed.

Where it runs

Surfaces and status.

WEB
Web · 1.1.0Live — site, review console, and embeddable question box all responding; the service health check on 2026-09-02 reported it up, with generated answers and semantic search both availableviavitna.com
API
Api · 1.1.0Live — an answer endpoint for your own systems plus a read-only, key-controlled connection for AI tooling; both live-verified during acceptance on 2026-08-24, including rejection of the wrong key classviavitna.com/docs.html
BOX
Appliance · image proven 2026-08-17/18; current source 1.1.0Sold to order — the sealed, encrypted, self-contained image with the models included was proven end to end on 2026-08-17/18: build, encrypt, unlock with the issued licence key, publish, and answer a cited question. No customer unit has been issued yet, and the proven image predates the 2026-08-24 hardening release, so a unit is built to current source at order time.viavitna.com/pricing.html
AND
Android · 1.0.0Built and signed at 1.0.0 (version code 1); passed acceptance on an emulator and on a physical phone on 2026-08-23. Not published to Google Play — as of the 2026-08-23 console check there was no store record and nothing uploaded. It is a client and needs a Viavitna you already run.viavitna.com

Status as of 2026-09-02. Checked live on 2026-09-02: viavitna.com's service health check returned ok with two live tenants and both generated answers and semantic search available, the pricing page served its published figures, and the Chinese edition served its own translated pages. Source version 1.1.0. Deployments are dated and written down: the security and privacy hardening went live 2026-08-24 as release 20260824T133701Z with live acceptance recorded in SECURITY-AUDIT.md and OPERATIONS.md, including a guarded switch that failed closed on a permissions fault and rolled itself back before passing on the second attempt; the current answer path was activated 2026-08-30/31 as release 20260831T015056Z after cold-start, cited-answer, and receipt acceptance recorded in OPERATIONS.md. The owned appliance lifecycle — build, encrypt, unlock with the licence key, publish, and answer — was proven end to end on 2026-08-17/18 per, on a build that predates the current source; no customer unit has been issued. The Android client is finished and signed but not on Google Play.

What is new

Recent progress.

This product ships often. The most recent verified changes, newest first.

  • /31 — the answer path was rebuilt so the AI models sit idle until a real question arrives and shut themselves down five minutes after the last one, cutting the running cost of an owned deployment without changing a single answer; activated as release 20260831T015056Z after cold-start, cited-answer, and receipt acceptance, with the timeouts widened so a genuine cold start is no longer mistaken for a failure.

  • the public site was rewritten end to end around a single offer, the no-charge content-fit review, with a pricing page carrying real published figures instead of a contact gate, plus a focused landing page and full Spanish and Chinese editions.

  • the pricing model was rebuilt around ownership rather than subscription, using cost figures measured on a live instance rather than estimated, and the retrieval engine was re-synchronised with its upstream so there is no divergence left to carry.

  • a large hardening release went live: the second, semantic verification pass that rejects generated text outright if it cannot run, tamper-evident receipts on every answer, mandatory question privacy with no opt-in anywhere, recoverable draft history with signed pagination, and a frozen quality gate that permits zero regressions before any model change ships; live-verified as release 20260824T133701Z, including migrating every older record to contain no question text.

  • the native Android client reached a finished, signed 1.0.0 and passed acceptance on both an emulator and a physical phone; it has not been published to the store.

Pricing

Published. Owned licence: $12,000 one-time plus $2,400/year for updates and support, or $6,000/year all-in. Hosted: $149/month Starter, $399/month Business, $899/month Scale — flat, never metered per question. Multi-site or multi-brand: $25,000–$75,000/year, scoped with your team. A content-fit review, in which we build a private draft from your material and test ten of your real questions, is offered at no charge and requires no purchase. The Android client has an intended one-time price of $9.99 but is not on sale yet, and it is only a client — it includes no server, tenant, hosting, or service plan.

Open Viavitna →
Honest by default. We publish the standard each product meets and the limits of each safeguard next to the feature, not in a footnote. If you cannot find an answer on this page, the assistant in the corner reads only these pages and will say so rather than guess.

Questions buyers ask

Straight answers.

What does it actually cost, and why is it not $49 a month?

An owned licence is $12,000 once plus $2,400 a year for updates and support, or $6,000 a year all-in. Hosted starts at $149 a month and never meters your questions. It costs more than a generic chatbot because it is a different thing: you own the whole system, your content never goes to an outside AI service, and there is no per-question meter behind it. If your budget is a cheap chatbot, we will tell you honestly that this is not a fit.

We already have a chatbot on our site. Why change?

Ask yours a question your policy answers plainly, then ask it something your site has never covered. Most will answer the second one anyway, confidently, with no source to check. Viavitna deletes claims it cannot tie to your text and declines when your content does not cover the question. The honest test is to run ten of your real questions through both, which is exactly what the no-charge content-fit review is.

Where does our content go, and who can see our customers' questions?

With an owned licence, nowhere. The engine, the AI models, and your content all sit on a machine inside your network, and neither your material nor your visitors' questions ever leave it. There is no outside AI service anywhere in the answer path in any configuration. On the hosted plan your content sits on infrastructure we operate — that is the one setup where it leaves your building, and we consider it the lesser choice.

How much work is it to move our content in?

Less than people expect, because there is nothing to rewrite or re-tag. Web pages, HTML, Markdown, and plain text go in as they are, and we can crawl your live site to build the first draft for you. Anything in another format has to be turned into text first, and the content-fit review is where we find out how much of that there is. Adding it to your website afterwards is a single line pasted once. The real work, when there is any, is fixing content the draft shows is unclear.

What if we stop paying?

A perpetual licence keeps working on the version you have — that is the honest behaviour for something you bought. Maintenance keeps the engine and the models current; letting it lapse stops the updates, not the assistant. We will also tell you the part vendors usually bury: the licence is enforceable, and a licence marked revoked stops the box answering, though a licence service we cannot reach never stops a paying customer. On hosted, export and wind-down terms are agreed before service starts, and moving from hosted to an owned licence later is a supported path we would rather you took.

Is it ready, or are we going first?

It is running today at viavitna.com, answering live questions with citations from its own published pages, and you can go interrogate it right now. Its deployments, security review, and acceptance runs are dated and written down, including one release switch that failed closed on a permissions fault, rolled itself back, and passed on the second attempt. The owned image has been built, encrypted, licence-unlocked, and proven answering end to end; yours would be built to current source when you order. We would rather show you the record than tell you it is mature.

What happens if the AI part goes down?

Your visitors keep getting answers, just plainer ones. When the writing model is unavailable, Viavitna quotes the relevant passage of your own content directly, still cited, or says plainly that the material does not cover the question. It is a downgrade in polish, never a downgrade in truthfulness, and it is the same floor that catches every other failure.

Can we prove what it told people, months later?

Yes, and this is one of the reasons people buy it. Every answer carries a receipt binding which version of your content was serving and which passages were used, and for any period a report can be pulled covering what was published, from which sources, how many questions came in, and every time it declined to answer. That report is produced without ever storing the words a visitor typed, and it proves what the system decided — not that your source material was itself correct.

Could someone trick it into ignoring its rules?

Your content is treated as reference material to quote, never as instructions to follow, and unsafe requests or attempts to fish for credentials are refused before anything else runs. The protection that actually matters is structural rather than a list of blocked phrases: even if an injected instruction were followed, the resulting text would be uncited and unsupported, and the verification step deletes exactly that. The pre-screen phrase patterns are written for English and Spanish; the structural check does not care what language anything is in.

How do we know it will not embarrass us on day one?

Because nothing you upload is public until you decide it is. Your material becomes a private draft that visitors cannot reach, and you spend as long as you like asking it the questions your team hears every week and reading the citations. Publishing is a separate, deliberate click, every earlier version is kept and hash-checked, and bringing an old one back puts it in review rather than on your site.

What should I know before I rely on it?

We would rather you hear this from us than discover it later. As of 2026-09-02:

  • It can only say what your content says. If your policies are vague, contradictory, or out of date, Viavitna will abstain rather than paper over the gap — useful, but it means content work is often the real first project.
  • Content has to arrive as web pages, HTML, Markdown, or plain text. There is no document or scanned-file reader: anything in another format has to be converted to text first, which we sort out during the content-fit review rather than after you have bought.
  • It does not look anything up. It cannot check an order status, an account balance, or a case number, because it has no connection to your records. Anything personalised needs a separate, scoped integration.
  • It is not an open-ended creative assistant. Ask it something outside your material and it declines. Buyers who want a chatty general assistant should buy a different product.
  • The list of questions it could not answer shows counts, languages, and the sources that came closest — never the words a visitor typed. That is the deliberate trade: you can find the gap, but you cannot read the message.
  • The smaller model that runs on the owned image sometimes declines a question it could have answered, particularly around relative dates and time phrasing. The result is over-caution, never invention.
  • The pre-retrieval refusal patterns for unsafe or account-lookup requests are written for English and Spanish phrasing. The structural protection — deleting any claim your own text does not support — is language-independent and is what actually carries the promise.
  • Answers are only as fresh as the version you published. The drift check compares content that has a live public page behind it; a page whose text is assembled in the visitor's browser is reported as unverifiable rather than guessed at, and nothing is ever republished automatically.
  • The owned licence is enforced: the disk is encrypted and your key unlocks it, and the box can be configured to check its licence status with us, which means a licence marked revoked stops it answering. An unreachable licence service never stops a paying customer, but you should know the mechanism exists before you buy.
  • The pre-launch security review and the ongoing quality gates are ours, run in-house and documented, not a certificate from an outside firm. We have not commissioned a third-party penetration test or a formal certification.

An answer desk that never makes things up

Answers your customers only from your own approved content, cites every claim, and runs on hardware you own.

Prefer email? contact@autosecurelogin.com