Studios under console and publisher NDAs run their builds on SpeedrunCI. Every layer, from the build machines to the vault, the app and the links you share, keeps one studio's work apart from every other studio's.
Builds run on SpeedrunCI's AWS infrastructure, or on your own hardware with the SpeedrunCI agent.
Every build runs on its own Amazon EC2 instance, never shared with another studio: started for that build, used by nothing else, and destroyed when it finishes.
Every disk is deleted with the machine. No workspace, no cache and no credential survives into the next build, yours or anyone else's.
Need caches that stay warm between builds? Your studio gets a dedicated pool. Its machines run your builds and nobody else's.
Console and mobile signing credentials and your source control tokens are encrypted before they ever touch storage.
Credentials are encrypted with AES-256-GCM. Each console or mobile signing credential gets its own random key, which is itself encrypted with a master key derived using PBKDF2-SHA512.
Source control credentials are decrypted when a build checks out your code, held as a temporary credential for that build, and deleted when it finishes.
iOS signing certificates are loaded into a keychain created for that build alone and deleted when it finishes.
Once saved, credentials and integration secrets are masked when you view them in the app.
Before the app returns a build, a log or a setting, it checks the request against the studio and project that own it. Every time.
Builds, logs, artifacts and settings are only returned to members of the studio and project they belong to.
Owners, admins and members at studio level, admins and members per project, and custom roles. Artists can start builds without being able to change pipelines.
Sign in with Azure AD (Entra ID) or Google Workspace, and require single sign-on for your whole studio.
Editor plugin and runner tokens are stored hashed, expire on their own, and can be revoked at any time.
If SpeedrunCI hosts your Lore repositories, your studio gets its own server rather than a share of someone else's.
Each studio's Lore server runs as a separate app with its own storage volume and its own IP address, and requires sign-in.
Studio owners and admins can take snapshots, set how long they are kept, and restore one when needed.
Builds can also run on machines you own, with the SpeedrunCI agent.
The agent connects out to SpeedrunCI. You do not open any inbound port, and builds run on your hardware.
The agent only installs updates signed with our Ed25519 key, and keeps its own credentials in the operating system's keyring.
Sometimes support needs to see what you see. That access is limited, time-boxed and recorded.
Staff can only view your account as a user after giving a reason. The session lasts at most four hours and is recorded with who, when and why.
When a studio is deleted, a cleanup job removes its workspaces, build artifacts, logs, disk snapshots and build jobs.
Bring your security and IT team to the pilot. We will walk them through exactly how your builds would run, which data leaves your network, and where it is stored.