API Keys
API keys authenticate deployments. They link uploads to your account.
Generating Keys
From the Dashboard
- Go to Settings (avatar menu → Settings)
- Click Generate New Key
- Copy the key — it's only shown once
From the CLI
When you're logged in and run netlaunch deploy without --key, a key is auto-generated for you.
Key Format
fk_a1b2c3d4e5f6... (fk_ prefix + 64 hex characters)
Using Keys
CLI
# Via flag
netlaunch deploy --key fk_your_key -s my-app -f ./dist.zip
# Via environment variable
export NETLAUNCH_KEY=fk_your_key
netlaunch deploy -s my-app -f ./dist.zip
CI/CD
Store the key as a secret in your CI system and set it as NETLAUNCH_KEY:
# GitHub Actions
env:
NETLAUNCH_KEY: ${{ secrets.NETLAUNCH_KEY }}
Security
- Keys are hashed (SHA256) before storage — the raw key is never stored on our servers
- The raw key is shown once on generation — save it somewhere secure
- Each key tracks usage count and last used timestamp
- Keys are tied to your user account
Best Practices
| Practice | Why |
|---|---|
| Use separate keys for CI/CD and personal use | Easier to revoke if compromised |
| Store CI keys as secrets | Never hardcode in source code |
Use netlaunch login for local dev |
No need to manage keys manually |
| Rotate keys periodically | Limits exposure window |