Worker and connection
The Worker connects out. Nothing connects in.
What runs on your servers, with what access, the one connection out, and what stays on the server.
What gets installed on my app servers?
The Virca Worker is a process on your server. It watches the server and runs the fixes your team approves. Installed with sudo. Runs as one system service, as root by default or as another user you choose. Some functions may need root. One outbound connection to Virca, no inbound port. Virca is served from a US region. Credentials stay on the server.
The Virca Worker, on your Linux and Windows servers
The Worker on every server. The fix runs right there.
One service per server, one connection out. The Worker opens that connection and sends the signal out on it. A fix can only call functions already on the Worker. It runs only on the servers you assigned.
Worker
The Worker collects data and runs the fixes your team approves on each server. Updates itself.
One outbound connection
One TLS connection to Virca. No inbound port, no VPN.
ActionBooks
Your engineer sets the scope. AI works within it. Your team approves it.
Record
Who or what triggered the run, what ran, where, and the result.
Reviewing Virca for your company? Send the questions to ask@virca.ai.
