01
What does the user get?
A personal AI cockpit for daily context, local files, chosen tools, model routes, automations, and exportable outputs. The goal is useful work done from the user's own context.
FAQ
The data boundary, in plain English.
Burnout Bytes is an AI outcomes platform for people who want useful daily briefings, tool orchestration, and exportable work without turning their private workspace into our hosted data store.
Plain answers
02
Do you store chats or personal data?
No. The public product preview has no accounts, forms, analytics, hosted chats, or lead database. The private cockpit is designed around local or user-controlled storage.
03
Where do logins and keys live?
With the user. Burnout Bytes assumes browser-authenticated sessions, local secrets, or user-controlled provider access. We do not want to keep your login credentials.
04
When does cloud AI get used?
Only when the user chooses that route. A task can stay local-only, use a local LLM, call a selected cloud model, or hand off to a user-approved service.
05
Can it run local-only?
That is a core mode. Users should be able to choose local models such as Gemma, Qwen, or other local LLM routes when cloud sharing is not the right fit.
06
How do outputs leave the workspace?
The user decides. Outputs can become Markdown bundles, PDFs, CSVs, media files, checklists, NotebookLM handoffs, or future MCP tool library shares.
Pricing
Pricing is not packaged yet.
The product is still being shaped around the data boundary first. For pricing interest, email info@burnoutbytes.com and we will respond directly.
ANo public plan tiers are finalized.
BNo public lead form is being added to capture your interest.
CEmail is the contact path: info@burnoutbytes.com.