Enterprise Feature — Service accounts are available to enterprise customers. Contact us to learn more.
Start with the basics
Create a service account
Add a stable identity from Settings. Give it a clear name and optional description so teammates know what it runs.
Generate API keys
Create keys for scripts, CI jobs, and other automated workloads. Key values are shown only once, so copy them and store them securely.
Attach Droid Computers
Create computers owned by the service account so long-running work can continue under the same identity.
Configure Git access
Use your organization’s GitHub App installation for GitHub. For GitLab Cloud, add a service-account GitLab token in Settings.
How service accounts work
A service account authenticates with a Factory API key and runs as its own principal. Sessions, computers, billing events, and audit surfaces are attributed to the service account instead of a human user. Service accounts must be active to authenticate. If you mark one inactive or delete it, new requests using its keys fail, and workloads depending on that identity should be moved or restarted with another account.Manage access safely
Use short-lived keys when possible
Use short-lived keys when possible
Set expiration dates for keys that are used in temporary automation. Short-lived keys limit the blast radius if a key is accidentally exposed.
Rotate keys regularly
Rotate keys regularly
Create a new key, update the workload, then revoke the old key. Regular rotation reduces the risk of compromised credentials.
Keep names stable
Keep names stable
Service account names are immutable identifiers. Create a new service account if you need a different name.
Delete when finished
Delete when finished
Deleting a service account revokes its access and cleans up owned Factory resources where possible.
Common use cases
CI/CD
Run release, testing, or deployment workflows without depending on one engineer’s account.
Slack automation
Configure channels or workflows to run Droid as a shared team identity.
Repository automation
Clone, push, and operate on repositories with credentials managed for the service account.
Persistent computers
Keep Droid Computers tied to an automation identity instead of a teammate’s personal account.