Trust and control

What Elewrk does to keep AI work permitted, reviewable and recorded. Everything on this page describes how the products work today.

Access

  • People join an organization by invitation only; there is no open sign-up into someone else’s organization.
  • Agency OS sign-in uses Google accounts, with no Elewrk passwords.
  • Roles decide what each person can use and see, and the server checks them on every request.

Separation

  • Each organization’s data is isolated by the database’s own row-level security, not only by application code.
  • The application connects with restricted database roles that cannot bypass that isolation.

Approvals

  • In Agency OS, nothing is sent to a client or changed in another tool without a person’s approval.
  • In Elewrk Studio, admins choose which tools must wait for approval before they act.

Record of what happened

  • Agent runs, sign-ins and security events are recorded for review.
  • Elewrk Studio shows usage by person and model.

Models and spend

  • In Elewrk Studio, admins decide which models may run; a run never falls back to another model.
  • A monthly budget stops new runs once it is reached.

Hosting and backups

  • Elewrk runs on DigitalOcean in Bengaluru, India.
  • Data is backed up every night.

Questions or a concern

Write to pavan@elewrk.com. We answer security questions directly.