Security

Reporting a vulnerability

Email info@eigon.io with steps to reproduce. We will acknowledge within three working days and keep you updated until it is resolved. Please give us a reasonable chance to fix an issue before disclosing it publicly, and do not access, modify or delete data belonging to other customers while investigating. We will not pursue legal action against good-faith research that follows this.

Tenant isolation

Each environment gets its own VPC, security groups and task role. Database access is granted to the specific security group that environment's tasks run under, rather than to a shared network range, so one tenant cannot reach another's data store even within shared infrastructure.

Secrets

Platform secrets are held in AWS Secrets Manager and injected into containers at runtime; they are not baked into images or stored in task definitions. Environment variables and secrets you provide are encrypted at rest, supplied to your containers at runtime, and are not displayed back in full once saved. Database passwords are generated per environment from a cryptographic random source.

Authentication

Sign-in supports GitHub and Google OAuth as well as email and password. Passwords are hashed with bcrypt. Sessions use signed tokens with a limited lifetime and can be revoked; the sign-in flow uses a short-lived, HTTP-only, same-site state cookie to prevent request forgery. Programmatic access uses scoped API tokens that can be revoked individually.

Access to production

Production access is limited to the people who operate the service, and administrative actions taken against an organisation are recorded in that organisation's audit log where they affect it.

Data in transit and at rest

Traffic to Eigon is served over TLS. Data at rest — databases, object storage and snapshots — uses AWS-managed encryption.

Spending protection

Every environment carries a monthly spending cap. Reaching it stops new deployments and scales compute down rather than letting cost run away unattended. We treat an unbounded bill as a security-adjacent failure, because in practice it is how a compromised account does the most damage.

Backups

Managed databases have automated backups with retention that varies by environment profile. Before infrastructure is reclaimed from an idle or failing environment, data stores are snapshotted first. We recommend keeping your own backups of anything you cannot lose.

What we do not claim

We do not currently hold SOC 2, ISO 27001 or similar certification, and we do not have a formal bug bounty. We would rather say so plainly than imply otherwise. If you need a signed DPA or a security review before adopting Eigon, contact us and we will work through it with you.

See also our Privacy Policy and Terms of Service.