Warpdrive account
Signs you in and knows which Warpdrive belongs to you.
Under the hood
Your computer does the work. Warpdrive keeps it connected.
Your Apps and working files live on the computer that runs your Instance. Your account, your Chat history, and remote access use Warpdrive's hosted services. You choose whether the AI runs locally or with a provider such as OpenAI or Anthropic.
One request, end to end
From your account to the AI
Each layer has one job. The location label shows where that job happens.
Warpdrive hosted
Warpdrive app
The screen you use on desktop, web, or phone.
Warpdrive Gateway
Checks access and routes each request to the right computer.
Your computer
Runs the engine and supplies the storage and processing power.
Apps, AI agents, and local data
Your created Apps run here, and their source and data are stored here. Chat history is kept by the control plane, which Warpdrive hosts unless you run your own.
AI provider or local model
The agent asks the model you chose. That model can be on your computer or in the cloud.
What runs where
Three places. Three clear jobs.
Warpdrive does not move your local work into its cloud just because you sign in.
Warpdrive infrastructure
The services that let the product know you and connect your devices.
- Account: sign-in, security, and ownership
- Plan: access, billing, and product features
- Store: catalog, downloads, and publishing records
- Control plane: Chats, including full message text, and orchestration state
- Remote relay: optional path back to your computer
Your computer
The place where your Warpdrive does its real work.
- Gateway bridge: accepts approved requests
- Engine: runs agents and app jobs
- Created Apps: served from your machine
- Local storage: Workspaces, App data, and each Instance's agent state
Your chosen AI
The model that answers the agent. Warpdrive lets you choose its location.
- Local model: inference stays on your computer
- Cloud provider: requests go to the provider you select
- Warpdrive AI: answered by Venice AI, an outside provider
- Your account: provider terms and usage charges apply
- Per agent: different work can use different models
Phone and remote access
Your phone is a remote, not the engine room.
The phone shows the app. Your computer still runs the Apps and agents behind it.
Your phone
Sends an authenticated request.
Gateway or relay
Routes the request to your paired Warpdrive.
Your computer
Runs the action and sends the result back.
Remote access does not open your computer to the internet.
Your computer starts an outbound, authenticated connection, encrypted in transit when the Gateway uses HTTPS. Approved requests, their responses, and terminal output pass through the hosted relay; your local ports stay closed.
If your computer is offline
Your phone cannot reach the Apps or agents running on it. Work already running locally may continue, but remote actions wait or expire. Warpdrive does not silently move the job to cloud compute.
Choose where the AI thinks
Local AI and cloud AI are different paths.
Your Apps and Workspace files stay on your computer either way. A cloud model still receives the prompt and task context sent to it.
Local model
The model runs on your computer, so the model prompt is not sent to OpenAI or Anthropic. It uses your hardware and can be slower or less capable than a large cloud model.
AgentModel on your computer
OpenAI, Anthropic, or another provider
The agent sends the prompt and any context needed for the task to that provider. Its privacy terms, data controls, model limits, and usage charges apply.
AgentProvider APICloud model
Local AI does not make all of Warpdrive offline. Account sign-in, the Store, updates, and remote access still need a network connection, and Chat history still goes to the control plane — hosted by Warpdrive unless you run your own.
Trust & privacy
Your files stay where you run them.
Warpdrive's hosted services run your account, keep your Chat history, and connect your devices. Your computer remains the home for your Workspaces and Apps.
Hosted services can access
- Your account, security, plan, and entitlement details
- Store catalog, download, and publishing activity tied to your account
- Chat and orchestration state, including full message text, kept by the hosted control plane
- Paired-device IDs, connection state, and bounded health or usage metadata
- Requests and results that must pass through the hosted relay while you use remote access
Hosted services cannot access by default
- Browse arbitrary folders or files on your computer
- Use your local terminal, apps, or agents without an authenticated request
- Keep a central copy of your Workspace files — source leaves only when you publish, push, use a hosted Instance, or let an AI provider read it
- Send local-model prompts to OpenAI, Anthropic, or another AI provider
Cloud AI is a separate boundary: the provider receives whatever prompt and task context the selected agent sends to it. Read Trust & Privacy.