Check where previews run
Expect previews to run on spare capacity in Peak’s shared bare-metal pool. Expect each preview to run in its own Firecracker microVM, the same isolation as a CI job. Expect Peak to delete the microVM when the preview stops.Check network access
Expect Peak to check access before any request reaches your preview.
Expect previews on peakview.now, a separate domain from peak.inc.
Expect Peak to make every cookie a preview sets host-only, so it never reaches another preview.
Expect Peak to remove its sign-in cookie before a request reaches your app.
Check how Peak handles your keys
Expect Peak to encrypt each value at rest with its own AWS KMS data key. Expect Peak to decrypt values only to start a preview. Expect values to reach the microVM over TLS after it boots, never on its command line. Expect Peak to mask your values in preview logs and the Peakviews check. Expect a preview to get only the keys you add and the values Peak generates. Expect no GitHub Actions secrets in a preview. Expect Peak to fetch your code with a short-lived token that can only read that repository. Expect no preview for pull requests from forks.Check GitHub App permissions
Expect the Peakviews GitHub App to ask for these permissions.
Expect it to receive pull request, push, and check run events.