security
An agent on a computer is a serious thing
Software that can see a screen and run commands deserves more scrutiny than a web app. This page describes current practice, without guarantees. It changes as afire matures.
Where afire is today
- Closed alpha. Access is by invite and capacity is deliberately small. There are no formal certifications yet (SOC 2, ISO 27001); security questionnaires are answered on request.
- Choose devices accordingly. Alpha means rough edges. Connect devices where early software is an acceptable risk, not the one system a business can't lose.
Practices
Signed updates
Releases are signed and verified before an update is applied.
Outbound-only agents
Devices connect out over TLS. The agent doesn't listen for inbound connections on the hardware it runs on.
Scoped tools
Agents receive only the tools the device supports and the session allows.
Accountability
- Actions are logged. Commands, input control, screenshots, and file operations are recorded with their source and time, reviewable per device.
- Two-factor auth. TOTP on accounts; administrative actions are audited separately.
Data
- Deletable. Deleting a device deletes its chat history and stored media. Chat attachments are stored unopened server-side and expire after use.
- Diagnostics are opt-out. Sharing diagnostic data is a setting, not a condition.
- Metered with caps. Usage runs against per-account daily and monthly ceilings, enforced server-side.
The privacy policy states what is collected and how long it is kept. The terms cover what the service is and isn't responsible for.
Reporting something
Found something? Use the request-access form on the front page and lead with the word security. Those go straight to a human. Reports are welcome, including during the alpha.