Connek

One workspace per client. Nothing crosses between them.

Connek is a desktop application for agencies and consultants. Every client you work for gets its own folder, its own confirmed mail, its own browser profile, its own notes, its own AI sessions and its own audit trail — and the app is built so that one client's context cannot reach another's. That isolation is the product. A feature that loosened it would be a net loss, and the codebase treats it that way.

The selected client is the boundary

Attachments are scanned on your machine, or they do not move

An attachment arrives into a quarantine under the client's own folder, under a neutral extension so it cannot be opened as whatever it claims to be, and it is checked against its declared type, its extension and its actual leading bytes. Before anything can preview, save or send it, a malware scanner running on your own computer has to return a clean verdict: Microsoft Defender on Windows, ClamAV on macOS and Linux.

Nothing is uploaded to a scanning service — not the file, and not a hash of it, because the hash of a contract identifies that exact contract to anyone else holding a copy. That means there is no cloud fallback and no way to skip the check: on a machine with no working scanner an attachment stays quarantined and undeliverable rather than being delivered unscanned. On Windows the scanner is already there; on macOS it is one install.

AI that only ever sees one client

Connek finds Claude Code and Codex CLI in fixed trusted locations and verifies the executable's signature, canonical path, parsed version and protocol before it runs anything. Each turn starts inside a deny-default operating-system container that can read that one client's folder and nothing else — no other client, no unrelated user data, no direct network. If containment cannot be established the turn does not happen; it never quietly falls through to a cloud provider instead.

Connected MCP servers reach the model only through the app. You grant one reviewed, read-only tool to one client and fix its account selector yourself; the model cannot change it, the app re-checks the tool's fingerprint before every call, and results come back as evidence rather than as instructions.

It asks for very little

There is no broad macOS grant. You choose the folders Connek may look in, and it looks only there. It does not request Full Disk Access, Accessibility, Screen Recording, camera, microphone, Bluetooth, location, Contacts, Calendar, Photos or Notifications. Your clients' files, mail and notes stay on your machine: there is no server here holding them.

Pricing

AUD 49 / month

This price is a placeholder. It has not been confirmed and will change before the product goes on sale.

Stripe is in test mode. Checkout will open and behave normally, but no card is charged and no subscription starts.

What it does not do

This list is kept honest against the capability matrix in the project's own README, and the build refuses to publish a page that claims anything the matrix marks unavailable.

This site

No analytics, no third-party scripts, no external fonts or images, no cookies, and no consent banner to dismiss because there is nothing to consent to. Nothing on this page follows you anywhere. The only request it makes is the one you make yourself by pressing the button. Every page runs the same single script — one script written in this repository, served inline, permitted by the hash of its own bytes. On the account page it signs you in, shows you your own subscription and starts your download. Behind the subscribe button it does exactly one thing: if starting checkout fails, you stay on this page with a sentence you can act on instead of being sent to a raw error. No page needs it to be read, and the subscribe button posts with scripting turned off entirely.