Your country's data stays in your country
Some institutions cannot put a citizen file, a call recording, or a patient note on a foreign public cloud. That is not a preference. It is a residency rule, a regulator, a board, or a ministry that already said no.
The promise is simple: your country's data stays in your country. AssistFlow Sovereign Stack is the on-premise AI employee for that mandate. Voice, website chat, and allowed messaging run inside the perimeter you already control — or in a national cloud in the same country. It is quoted after a residency discovery, not a public-cloud signup.
Read the institution page at assistflow.ai/on-premise-ai. Turkish institutions use assistflow.ai/on-prem-yapay-zeka. This article is the same offer in editorial form: who it is for, what stays inside the border, how placement works, and how to start without sending a server diagram to a web form.
Who this is for
Public sector teams that must keep citizen conversations inside national borders. Banks and holdings that cannot park KYC files or call recordings on a foreign SaaS. Hospitals and clinics that keep intake, appointments, and voice notes in the health system's country. Energy, transport, and campus operators with an air-gap or national-cloud mandate.
If you can run a normal AssistFlow Cloud workspace, this page is not the product you buy first. Cloud chat, WhatsApp, and phone AI for stores and hotels stay on the public plans at trial-signup. Sovereign Stack is the lane for records that must not leave.
What stays inside the country
Conversations stay. Voice calls, website chat, and allowed messaging threads are stored where you place the stack — not on a consumer AI that trains in another region.
Documents and knowledge stay. Policies, FAQs, and internal files used to answer remain in your archive. Recordings and transcripts stay under your retention rules and legal hold. When a person takes over, the thread stays on the same in-country operations screen.
Human handoff is part of the product on every AssistFlow surface. Sovereign placement does not remove the human; it keeps the handoff in the same country as the bot.
Placement the institution chooses
Three placements, one promise. Your data center: software runs on racks you already operate, and updates follow your change window. Same-country national or public cloud: data remains inside that country's border. Isolated or air-gapped: no outbound path; licenses and updates arrive as a controlled package.
AssistFlow Cloud is a different SKU. This article does not sell that signup. Hardware, models, and rack drawings belong in the discovery, not on the public form.
How a residency conversation starts
The public form asks for a name, a work email, the institution, the country, and an optional note about which conversations or files cannot leave. That is enough to book a discovery with security, legal, and IT. It is not a request for GPU counts or a model shortlist.
After that call, AssistFlow writes a residency plan and a quote. Sector landings still exist for demos — government AI, banking AI, hospital AI — but those pages are product tours. The residency offer lives on the on-premise page.
What this is not
It is not a 14-day chatbot trial with a credit card. It is not a promise that every country already has a rack waiting. It is not a dump of internal lab names. If you need the self-serve website plan, use contact or the trial. If the records cannot leave the country, use the on-premise inquiry.
Security and compliance language for the cloud product remains at security-compliance. Sovereign Stack adds a placement choice on top of that: same country, your perimeter, your change window.
Start with the country, not the stack
Write the country and the records that must stay. AssistFlow will not ask you to design the inference layer in a browser form. The AI employee — voice, chat, knowledge, handoff — is the same idea as the cloud product. The difference is where it is allowed to live.
A ministry that answers citizens on the phone cannot treat that audio as a disposable SaaS clip. A bank that identifies a caller cannot drop the recording into a consumer model that trains in another region. A hospital that books an appointment cannot put the name and the complaint on a foreign inbox. Those are the conversations this page is for.
Teams often arrive with a demo of the cloud widget still open in another tab. That demo is useful to feel the employee. It is the wrong contract for residency. The government, banking, and hospital landings show a sector voice. They do not promise that the bytes stay in your country. Only the on-premise inquiry does.
Discovery usually covers four questions. Which conversations are in scope. Which files the model is allowed to read. Which network the employee is allowed to call. Who on your side signs the change window. Answers to those four questions are enough to write a placement plan. They are not enough to publish a rack list on the internet, and we will not ask you to.
If legal already wrote “no foreign public cloud,” bring that sentence. If a national cloud already exists, bring the region name. If the site is air-gapped, say so in the optional note. AssistFlow will not turn the form into an RFP. Sales and security will ask for diagrams on a call, under your rules.
Existing AssistFlow customers sometimes split the estate: a cloud workspace for the public website, and a sovereign placement for the regulated line. That split is a design choice, not a default. The inquiry form does not assume you want both. It assumes you have a country and a class of records that cannot leave.
Operators who already run AssistFlow Voice or Omni Inbox in the cloud can keep that workspace. Sovereign Stack does not delete it. It adds a placement for the conversations that a regulator already ruled out of the public cloud. The employee still greets, answers, and hands off. The bytes do not take a foreign hop to do it.
Request a residency conversation on the on-premise AI page, or email sales from that form. Keep the files in the country that owns them.