Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-05

CI/CD security

Encrypted token, credentials that never travel, approval separate from the requester and an audit trail.

  • Encrypted token. The Git token is stored encrypted (AES-256-GCM), never goes back to the screen and never appears in an error message.
  • Credentials do not travel. Neither to the repository nor from Development to Production. Each environment uses its own connections.
  • Separate data. Each environment reads and writes only its own datasets.
  • The requester does not approve. The rule always applies, even to administrators.
  • Nothing overwrites someone else's work in Git. If someone changed the branch midway, ingestia stops and warns — it does not force.
  • Self-hosted server address (GitHub Enterprise, self-managed GitLab) only with https and a public address.
  • Audit. Connecting the repository, creating Development, requesting, approving, rejecting, deploying and rolling back are recorded in Audit.

Related links