/ SONDA · AUTOMATE

An assistant with your key, and your finger on the button.

Themis explains an answer, writes a request's script or its checks, imports a spec from a URL, builds a mock, builds a whole app — through Sonda's own validated code, never by running text the model produced. Sending a request, deleting anything or running a folder becomes a button in the chat that you press, or do not.

BRING YOUR OWN KEY ANTHROPIC · OPENAI · XAI · LOCAL 42 TOOLS NOTHING OF THE CONVERSATION WRITTEN

At a glance

ProvidersAnthropic, OpenAI, xAI, or any OpenAI-compatible local server — Ollama, LM Studio, vLLM. The model name is typed and sent unchanged; there is no list to go stale.
KeysOne per provider, sealed under the account password, never handed to the window. Provider addresses are fixed in the code; only the local one can be changed.
SeesThe question, the last twelve turns, and — if you leave the box ticked — the active tab: method, URL, headers with secrets hidden, the body cut short, the last answer, the test results.
KeepsNothing. The conversation lives in memory while Sonda runs; lock or quit and it is gone.
Shared seatAn administrator shares one provider and key per division; members with "Use Themis AI" use it, decrypted in memory, never written to their disk, never shown.
/ YOUR KEY, SONDA'S CODE

The model proposes. Sonda's own code does it. You press the button.

Themis talks to the provider you pick — Anthropic, OpenAI, xAI, or any OpenAI-compatible local server — with your key, sealed under the account password and never handed to the window. The provider addresses are fixed in the code; only the local one can be changed. It sees the question, the last twelve turns and, if you leave the box ticked, the active tab: method, URL, headers with secrets hidden, the body cut short, the last answer, the test results.

What comes back is a tool call, and a tool call runs the same validated function a click would, under the workspace lock, with the member's permissions checked. The model's words never become code. Sending, deleting and running a folder wait in the chat for your click — and the conversation lives in memory while Sonda runs: lock or quit and it is gone.

What leaves this computer
/ WHAT IT DOES

Forty-two tools, all of them Sonda's own code.

A tool call runs the same validated function a click would, under the workspace lock, with the member's permissions checked. The model's words never become code.

Reads and explains.

Explain this answer. Why is this broker pane amber. What does this flow do. Read a device's last values. List the projects, the flows, the Echoes, the apps.

Builds from the document, not from a guess.

A project from a documentation URL — it fetches the page, finds the OpenAPI, WSDL, OData or FHIR document behind it, and imports it rather than guessing. Folders, requests with any body type, variables, auth told to use placeholders and never real values, checks from the last answer, a script into the editor.

Mocks and apps, tried before they are handed over.

An Echo with a realistic data set and endpoints answering by data, body or script. An app with containers, screens, a dashboard, watchers and functions — tried before they are handed over. An On watch from a device to a request.

Proposes, and waits.

Send this request. Delete this. Run this folder. Each one is a card with No and the verb, and Show me to open it on screen first — on all but a delete. The outcome comes back as a turn. A delete re-checks the permission at the moment you press.

Refuses what is not its to do.

Frozen, locked and paused items. Anything the member's flags do not allow. Submitting, approving, locking, pausing and merging — never Themis's. Off for app runners and while Sonda is locked.

Guards against what it reads.

Every tool result and every screen block is sealed as untrusted data with a random nonce, and the system prompt says not to follow instructions inside it. About thirty injection phrases are removed visibly, with a line that says so. Web reads only from hosts named in the conversation, GET only, 16 MB.

/ THE RULES

What Themis does without a click, and what she never does.

Said exactly, because the difference matters in a regulated environment. Building is Themis's: a project, a mock, an app, a check, each step shown as it goes. Sending, deleting and running a folder are yours: a card in the chat, with the verb on the button.

Beside it, one turn: a question with the request on screen, two changes made without asking, and a send that waits for the person.

# Themis AI · Payments · kept while Sonda is open you Why does POST /orders answer 422 here? [x] Include POST /orders # as data, secrets hidden themis The body has no currency. I added it from the spec, and a check on the status. update_request body.currency ✓ done add_check status is 201 ✓ done Send POST /orders — to see the new answer [ No ] [ Show me ] [ ▶ Send ] # your click ✓ 201 · 180 ms # back as a turn you Delete the old orders/v1 folder too. themis Delete orders/v1 — 6 requests [ No ] [ Delete ] # the permission re-checked the moment you press
Without a clickReads. Builds projects, mocks and apps. Imports a spec. Runs a flow you ask it to run, and tries a function or a watcher it just wrote. Calls a tool on an MCP server you connected, and answers that server's sampling requests with your model.
With a clickSends a single request. Deletes anything. Runs a folder. These three are always a card in the chat that you press.
/ LOCKFLARE SONDA

Themis, in the free edition. The key is yours.

Themis AI, listed →