Security
How Ark is built, and why.
This page describes Ark's architecture in broad strokes: where a household's data lives, how members and apps are kept apart, and how the AI assistant acts for a member without holding their keys. What leaves the house is on the front page, under Three things leave the house.
One machine, in your home
Ark is a single appliance on the household's own network. The apps, the databases, the files and each member's assistant all run on it. There is no Ark cloud holding a copy. A cloud service protects your data with promises about how it will be handled; Ark starts from where the data is.
Four layers, each with one job
The appliance is built in layers. The lowest runs the machine and the home network. Above it, a container platform runs everything else. Above that sit the services every app shares: sign-in, storage, routing, certificates, DNS filtering and access to outside accounts. The apps and the assistant are on top.
Each layer talks only to the layers next to it. An app does not manage its own sign-in, storage or outside connections. It asks the platform, and the platform decides. That keeps the security-critical work in a few services, not repeated in every app.
Every member is their own person
Each member has one account and signs in once for every app. A member's notes, files, mail and calendar are stored under that member, and the content store checks the member on every read and write, at the database itself. Sharing is something a member does on purpose: with the household, or with one other member.
Apps never hold your outside keys
When a household connects a Google account or a model provider, the key is kept by one service whose only job is to hold such keys and make the outside call. Apps and assistants ask that service to act. They never see the key, so a fault in one app cannot leak it.
The assistant acts for you, not as you
Each member has an AI assistant, and each assistant runs in a sandbox of its own. The assistant holds no password and no key. When it needs to do something for a member, the platform gives it a token that lasts one minute and works only for what that member has allowed. Every permission is listed on a page the member can read, with a switch beside it.
The credentials the assistant's tools rely on sit in a separate, locked part of the sandbox that neither the AI model nor its tools can read. We designed it this way because an assistant reads things other people wrote, such as web pages and email, and that text can try to give it instructions. The design assumes this will sometimes work, and limits what the assistant could then reach.
Away from home
Nothing in the home answers an unknown caller from the internet, and the household's router opens no port. A member's phone reaches the household through an encrypted tunnel whose keys exist only on the phone and the appliance. When the two cannot reach each other directly, a relay that Teknios operates passes the traffic along. The relay holds no key and cannot read what it carries. Outside access is off until the household's admin turns it on, app by app.
We test it as if it had already failed
We test the appliance on the assumption that an assistant has been taken over, and check from inside its sandbox what it can actually reach. We trust the result of an attempt, not the configuration that says the attempt should fail. What we find, we fix and test again.
Who we are
Ark is built by Teknios. Questions about any of this: [email protected].
Last updated 21 November 2026