Security you can inspect.
Arctite's security model is based on visible boundaries, explicit permissions, exact payload review, and locally enforced execution rules.
How context moves - and where it stops.
The pipeline below runs on your machine. Redaction, freezing, and digest binding happen before anything is eligible to leave.
YOUR MACHINE
the full pipeline runs locally
EXACT APPROVED PAYLOAD
The frozen package bound to its digest. Nothing else leaves the machine. No retries re-send it without a new review.
USER-SELECTED PROVIDER
Context is assembled locally.
Development context is collected and assembled on your machine, per project. The Context Engine has no cloud component, and no intermediate state is uploaded while a package is being prepared.
Only sources you enable.
Every observation source is explicit and shown on one screen. What is not listed here is never gathered.
OBSERVATION SOURCES
per projectApproved sources
- Filesproject scope only
- Gitdiff · log · branch
- Terminal metadatacommands · exit codes
- Browser contextactive tab · page title
- Clipboardmanual share only
- Notesproject notes
Never captured silently
- Keystrokesnever captured
- Cookiesnever captured
- Screenshotsnever captured
- Mouse inputnever captured
- Browser storagenever captured
Permission set is explicit, project-scoped, and re-confirmed on change.
Never captured
- Keystrokes
- Cookies
- Screenshots
- Mouse input
- Browser storage
- Silent browser observation
Local redaction happens before submission.
Sensitive values - API keys, tokens, credentials - are detected and removed while the package is still on your machine. Redactions are counted, listed, and visible in the preview.
- Secrets are removed from context before provider submission
- The redaction count is part of the reviewed package
- Redacted values never appear in the outgoing payload
- Redaction rules are local and project-scoped
Exact Context Preview. Then freeze.
The developer sees the outgoing context package item by item. Reviewing it freezes the package; freezing binds it to a digest. Only the frozen package can be approved - and the digest is part of the record.
CONTEXT PACKAGE
Files
Git
Terminal
Browser
This exact package, and nothing else, is what gets sent.
Frozen 23:14:08 · sha 7e3b0f…a91c
Bring your own key, choose your provider.
Inference goes to a provider you select - OpenAI, Anthropic, OpenRouter, or a local model. You configure the endpoint and the key. Arctite does not route inference through its own project-data plane.
OpenAI
your key, your endpoint
Anthropic
your key, your endpoint
OpenRouter
your key, your endpoint
Local models
never leaves your machine
Agent Cycle security is enforced locally.
Provider plans are validated against project permissions before execution. No arbitrary shell, no silent retries, no invisible writes - and one action at a time.
- Provider plans validated locally
- No arbitrary shell
- Fixed approved checks only
- Typed actions, project-scoped permissions
- File writes require approval
- No silent retries
- One action at a time
- Context-plan binding via digest
- Verification before the next action
AGENT CYCLE
- Assemble context
- Review frozen package
- Write src/session.tsawaiting approval
- Run verification
Proposed write
+14 −7
Type “approve” to execute this step
The cloud boundary.
Arctite may use cloud services for authentication, subscription state, licensing, and organization or team controls. Developer context and project activity are designed to remain outside an Arctite-hosted project-data plane - the inference payload you approve is sent to the provider you chose, and nothing else is.