Skip to content

Zero Trust

← Back to standards

Four ideas we are standardizing on:

Production changes leave a reviewable trail—GitHub commits, Actions runs, and deploy history—not one-off laptop deploys.

People and automation get only what they need for their tier: separate Fly orgs, scoped tokens, and IAM aligned to the job—not broad production access for daily dev work.

Never trust the network by default. APIs reach users through Cloudflare Tunnel and private .internal origins; access is explicit, not “already inside the firewall.”

Production deploys run through CI/CD on main (fly-deploy-main.yml). No flyctl deploy to the production org from a developer machine.