Engineering standards
What every project gets, whoever is on the team. Ask us to show any of this in your repository during week one.
What blocks a merge
- A failing test, type check or lint.
- A failed build or preview deployment.
- A high-severity security or dependency finding.
- An open review comment that hasn’t been resolved.
- A database migration without a tested rollback path.
Tests
- Automated tests on the rules that matter: money, permissions and data access.
- End-to-end tests on the critical flows, such as sign-up, checkout and booking.
- The full suite runs on every pull request. Bessit runs 700+ tests, WahaSend 1,000+.
Continuous integration
- Every pull request builds, type-checks, lints and tests before review.
- Every branch gets its own preview deployment you can click.
- The main branch is protected: changes land only through reviewed pull requests.
Security and dependencies
- Automated dependency and vulnerability scanning, with updates reviewed every week.
- Secret scanning, and no credentials in the codebase.
- Access checked on the server and enforced in the database, never only hidden in the interface.
- Audit logs for every admin action that touches money or users.
What you get at handover
- The source code repository, transferred to your organisation.
- Hosting, app store and third-party accounts in your name.
- Credentials rotated and handed over in a password manager.
- Architecture notes, setup guide and a runbook for common operations.
- Design files and brand assets.
Tell us what you’re building.
A few lines are enough. The founder replies within 24 hours.