Kian is Proofline's model of what runs where, who can reach what and which limits bind in your AWS and Google Cloud environments. Every answer is checked against it, says how fresh its evidence is, and says what it does not know.
Scale API to 12 tasks by you · Pull Request #42 · your-org/your-repoRestrict access to application config by you · Pull Request #43 · your-org/your-repoMove database access to the worker group by you · Pull Request #44 · your-org/your-repoRename the order status column by you · Pull Request #45 · your-org/your-repo
github.com/your-org/your-repo/pull/42/files
Capacity overruns
A one-line change to a task count. The failure lives in the database’s connection limit, which the diff never mentions.
The startup code calls GetObject without a version ID. The replacement permission allows versioned reads only, so the request is denied and the API cannot start.
View evidence
Code
infra/iam/api.tf:24 replaces s3:GetObject. src/config.ts reads prod.json without a version ID before starting the server.
Environment
The pinned environment snapshot links the API task to this role. No other applicable policy grants s3:GetObject on the configuration object.
Keep s3:GetObject scoped to app-config/prod.json. The API needs that action to load its configuration.
2525 }
Network outages
A security group swap that is right for the worker. It removes the only path the API has to the database.
This replaces the database’s only ingress rule for the API security group. API tasks still connect to orders-prod:5432, so new connections time out after the rule changes.
View evidence
Code
infra/network/database.tf:31 replaces the allowed source group. The API still opens PostgreSQL connections during startup and when its pool reconnects.
Environment
The pinned snapshot places API tasks in the API security group and the database in the group changed here. No other ingress rule allows that source on TCP 5432.
Retain the API security group in the database’s allowed sources. Add the worker group alongside it if both services need access.
3232 }
Breaking migrations
The rename is sound on its own. The release that is running still reads the old column.
Openyou want to merge 1 commit into main from rename-order-status
Conversation1Commits1ChecksFiles changed1+1−0
Filter files…migrations018_order_status.sql
migrations/018_order_status.sql+1−0Viewed
@@ -0,0 +1 @@
1+ ALTER TABLE orders RENAME COLUMN status TO state;
prooflinebotnow
The running API still queries the old column
The migration renames orders.status before the API rollout. The currently deployed release still selects status, so order requests fail with a missing-column error while that release is running.
View evidence
Code
migrations/018_order_status.sql:1 renames the column. The deployment configuration runs migrations before replacing API tasks.
Environment
The recorded production deployment identifies the running image and its commit. At that commit, src/orders.ts queries orders.status.
Use an additive migration first. Add and backfill state, deploy code that supports the transition, and remove status after old readers are retired.
Install the GitHub App for the repositories you choose, then grant read-only access to the infrastructure in the target environment. The required permissions depend on the services you connect. Read about security and data access.
Can it change my infrastructure?
Proofline never mutates your infrastructure or merges changes. Your team decides how to act on its findings.
What happens when evidence is unavailable?
Proofline keeps the assessment incomplete and puts evidence gaps in console setup tasks. Supported findings still reach your team. An absence of findings does not establish that a deployment will succeed.
Does it replace tests or staging?
Keep your tests and staging environment. Proofline adds a review of the change against evidence from its target infrastructure, helping you investigate risks that depend on that environment.
Can I start for free?
Yes. New organizations get one calendar month of hosted code review from GitHub App installation. Private and public repositories are included, with no card or cloud connection required. Fair use applies. Read the free-month terms. Existing signup and environment-ready credit grants are separate. Every plan includes unlimited people. Compare workspace plans.
One month of free code review
Try hosted review on your GitHub pull requests, in private or public repositories. No card or cloud connection required. For new organizations; fair use applies.
Connect GitHub
Sign in and install the GitHub App on the repositories you choose. Your free month starts at installation.
Choose a repository
Start with one private or public repository. You do not need to connect a cloud account.
Open a pull request
New organizations start with automatic code review enabled for their selected repositories.
Inspect a review
Read findings and their cited evidence on your pull request. Use the console to check connection health and setup tasks.
Database connections run out before all tasks become healthy
Each task opens 20 connections before passing its health check. With 12 tasks, the service needs 240 connections. The production database allows 197.