You use an approved workspace. Cloud accounts, workers, and runtime secrets are not a self-serve install in these docs.
Deployment model
These guides assume an approved Bundata workspace that you can already open. They are not instructions to install Bundata on AWS, Azure, Google Cloud, or your own servers.
| Piece | Client administrator | Bundata operator |
|---|---|---|
| Users and roles | Yes | When enrollment is closed, grants may require Bundata |
| Organization generation key | Yes, owner or admin | No |
| Local embedding sidecar | Yes, if you choose that profile. You run a reachable sidecar | The API must be allowed to call the URL you saved |
| Voyage embedding credential | No | Yes, when that profile is selected |
| Object storage and workers for stored uploads | No, unless your agreement says you operate them | Yes |
| Source credentials | Yes, least privilege on your bucket or database | No |
| DNS and production activation | No | Separate from this documentation |
Older pages that described a self-serve cloud or open-source install now redirect here. A deployment name in a menu is not a provisioned environment.
If upload returns S3_NOT_CONFIGURED or DOCUMENT_PROCESSING_QUEUE_UNAVAILABLE, the stored path cannot finish. Escalate to the operator with the code. Do not ask a client user to paste infrastructure credentials into chat.