buildHow we handle money, code and access.
Clear controls, visible work and no lock-in. Your buildroom shows the project record as it changes.
Milestone funds
Payments run through Stripe. Milestone funds release after client approval or the agreed review window.
Code ownership
Paid milestone work is assigned to you. The repository can move to your own GitHub account.
Visible work
The buildroom shows tickets, commits, repo files, checks and review notes as the work moves.
Project record
Approvals, comments, payment events and delivery records stay attached to the project.
Payments
- Stripe handles card details. We do not store full card numbers.
- Each milestone has its own funding, approval and release state.
- Release is tied to client approval or the agreed review window.
- Refund requests before approval are handled through the milestone ledger.
Access and security
- Passwords are hashed with scrypt and per-user salts.
- Sign-in uses server-side sessions and HttpOnly cookies.
- Buildroom access is scoped by project.
- Repository access is granted by project and can be revoked.
Sub-processors
| Provider | Purpose |
|---|---|
| Stripe | Payments |
| Railway | Hosting |
| GitHub | Code hosting and repo access |
| Resend | |
| Jitsi | Video calls |
| Anthropic | Planning and summary generation |
How we work
- Review before release. Work waits for client approval before milestone funds release.
- Evidence beside the work. Tickets link to commits, files, checks and notes where available.
- Delivery record. Completed work can be recorded with milestone status, ownership and invoice links.
- No lock-in. You can take the code and project records with you.
Documents
Questions about security or trust? support@buildquarter.com