Emissario serves your site from git and answers your visitors with an AI agent that follows your instructions and your token limits. Analytics without cookies, a contact inbox, two-factor sign-in, backups and LGPD/GDPR privacy controls come in the same binary.
You are chatting with an AI, not a person. It can make mistakes. Your messages are sent to an AI provider (see Privacy): do not share sensitive personal data.
A real conversation with this site's agent, served by Emissario. How it works
Write its instructions in a git repository, pick any OpenAI-compatible model and decide how many tokens it may spend. Emissario signs the history, enforces the limits and never stores a conversation.
The agent reads instructions/README.md and any file of its repository, synced like your website. A commit changes what it knows.
Output tokens per call, tokens a day for everyone, tokens a day per IP, requests a minute — and the usage by day and by IP in the backoffice.
Learn moreWhen a visitor asks, the model writes an anonymous summary for your team, and a second pass masks emails, phones, CPF, CNPJ and cards.
Learn moreIt says it is an AI in its first answer and whenever asked. The conversation stays in the visitor's browser, signed so no one can forge it.
Learn moreThe agent overview shows whether the chat is answering, the tokens used today against the daily limit, the IPs that reached their own limit and the latest summaries. The usage page breaks it down by day and by IP.
Your site and your agent's instructions live in git. Emissario pulls both, serves the pages, answers the API calls and keeps every record encrypted in one folder.
frontend/: static files, as committed. Publishing is a git push.
instructions/: README.md, SUMMARY.md and any file the agent may read.
Pages, the AI chat and the contact form. No cookies.
Any OpenAI-compatible provider, or a local Ollama.
The backoffice at /admin, with two-factor sign-in.
No database server, no analytics service, no runtime to install. Every feature below ships in the same binary and is documented on GitHub.
The server records the page, time, country, device, browser and OS of every view. No cookie, no script, no third-party service: even the country is looked up locally.
DetailsAny JSON your form sends, kept as sent with its time and country, limited per IP. Search, archive and erase it.
DetailsEvery backoffice user can protect their account with an authenticator app (TOTP).
DetailsRoot and viewer users, and API tokens shown once, with an expiry and the IPs allowed to use them.
DetailsTurn away an IP, a CIDR range, a hashed IP or a whole country before any route reads the request.
DetailsTeach Claude Code, Codex and Antigravity the routes your site calls and the files your agent reads.
Details
Encryption at rest, hashed IPs, retentions enforced every hour, find and erase, legal holds, a Marco Civil access log and LGPD/GDPR presets.
Details
Snapshots of every database, taken in the background, downloaded as a zip, uploaded and restored — put back as they were if a restore fails.
DetailsServes the frontend/ folder of a repository and keeps it pulled. Publishing is a git push.
Automate the backoffice under /api/admin, and import /openapi.json into Postman or Swagger.
Security and privacy are the defaults, not add-ons. Every risky choice comes with a notice that names the law it touches.
$ export EMISSARIO_ENCRYPT_KEY=$(emissario generate-encrypt-key)
$ emissario add-backoffice-user --username admin \
--email admin@example.com --role root
$ emissario start-serverInstall it yourself at no cost, or have its creator set it up for you.
Emissario is free under the MIT license. Install the binary, create a backoffice user and point it at the repository of your site.
Mateus Moutinho, the creator of Emissario, sets it up privately on your server: the install, HTTPS, the encryption key and backups, the backoffice users, the website and agent sync, and the privacy settings.