Where your
information goes.
Your equipment. Your accounts.
A clear say in what connects.
Local hosting gives your business meaningful control. It still needs careful permissions, secure devices and sensible decisions about outside services.
On equipment your business owns
Connections are a choice, not a hidden fallback.
A local core.
Explicit connections.
In the intended setup, equipment in your office processes confidential prompts and files without sending them to an outside AI provider. Sensitive storage and sign-in also run locally; the system does not require an Outpost-hosted login, licensing server or cloud identity provider to be usable.
This describes the intended customer setup and its limits. Development and installation checks have started. Production qualification is incomplete, and customer installations have not begun.
Where information lives.
In the intended setup, your questions, files and AI outputs stay within the customer-controlled system. Accounts, passwords, sign-in sessions and account recovery run there too.
System records can show errors, account activity and backup status. What they contain, who can read them and how long they are kept must be agreed during setup. Routine support should use these records instead of reading your work.
There is no hidden cloud inference fallback. An approved outside connection can change where particular information travels, so those choices are explicit.
The right people.
The right access.
Each employee uses their own account in a company-branded browser workspace. Permissions and authorized context matter: an assistant should work with the information that person is allowed to use.
Individual accounts exist in development. Separation between a person’s different projects, how long information is kept, and which files the AI can reach still need further work and testing.
Customer-domain access through an ordinary browser is the selected direction, including authorized remote use. Deployment and security qualification remain outstanding. Remote browsers receive information on those devices; device security and your access policy remain part of the picture.
You decide what connects.
Outside tools, external identity connections and other services require explicit choices. They can send information beyond your equipment, introduce separate accounts or charges, and bring their own terms and data practices.
The intended process finds and prepares a useful new capability, then asks for a short approval before enabling it. The approval should show who published it, what it can access, any outside services and the cost. More access requires another approval. This automatic preparation process is still being developed.
New account connections, spending permissions and changes to the data boundary are separate owner decisions. Local-only use and explicitly authorized cloud development stay separate.
Help, with permission.
Routine care checks whether the system and backups are working, and whether updates are worth testing. It should not require routine reading of your confidential work.
Exceptional content access requires your authorization. We do not claim that administrators are technically incapable of seeing information. Access arrangements, limits and any remote support route must be agreed and implemented for your installation.
Optional care has agreed hours, response windows and scope. It does not mean 24/7 coverage, unlimited requests or continuous custom development.
Keep control.
Plan for recovery.
The intended backup plan uses encrypted copies under your control, such as local or network storage with an agreed schedule for rotating copies. Cloud backup is not the default promise. Recovery procedures, backup checks, retention and deletion must be agreed for your needs and verified before relying on them.
You own the equipment and data. Setup and administrator handoff without ongoing Outpost care is a genuine option.
If care ends, the intended policy is that you retain the hardware, data and agreed installed-system use. The handoff includes removing Outpost’s access. There is no remote kill switch. Final handoff obligations and installed-software licensing terms need contractual definition.
Local is a boundary.
It is not a guarantee.
Local hosting does not by itself prevent a compromised device, incorrect permissions, lost hardware or an unsafe outside connection. Separate user settings alone do not prevent access to other files. We must test which files, services and accounts the AI can actually reach.
AI can make mistakes, invent details and misunderstand instructions. Review facts, calculations, advice and commitments before using an answer. Legal and financial work still needs appropriate professional review.
No blanket security certification, regulatory compliance or model-performance guarantee is claimed. The repeatable customer installer, intended equipment, workload, isolation and deployment/security checks are not fully qualified. A successful development example is not a production installation.
Start with your boundaries.
Bring the kinds of information you handle and one nonconfidential example of useful work. That is a better starting point than a hardware specification.
Let’s talk private AIReturn to Outpost