Yours from the
first commit.
A development partner who holds your repository, your cloud account or your domains holds your business. Ownership here is settled at contracting rather than promised at handover.
Everything built
for you.
Written into the Master Services Agreement before work starts, not negotiated when the relationship ends.
| Asset | Held in | From |
|---|---|---|
| Source code repository | Your GitHub / GitLab organisation | First commit |
| Cloud infrastructure | Your AWS / GCP / Azure account | Day one |
| Domains and DNS | Your registrar account | Day one |
| Design files | Your Figma workspace, with edit rights | Day one |
| Third-party accounts | Your billing, your credentials | Day one |
| Intellectual property | Assigned to you by contract | On creation |
| Customer and product data | Your infrastructure, always | Always |
| Documentation | Delivered at handover, yours to keep | Handover |
Akontec retains only its own pre-existing internal libraries and tooling, which are licensed to you perpetually and royalty-free for use in your product. That carve-out is listed explicitly in the agreement rather than buried in a definitions clause.
Controls in the build,
not just the contract.
Security work that happens during development costs a fraction of security work that happens after an incident.
Application security
- Parameterised queries, no string-built SQL
- Input validation and output encoding
- Password hashing to current standards
- Role checks enforced server-side, always
- Rate limiting on authentication and public endpoints
- Dependency scanning in the pipeline
Infrastructure security
- Environment separation with no shared credentials
- Secrets in a manager, never in the repository
- Encryption in transit and at rest
- Least-privilege IAM roles
- Automated backups with restore testing
- Audit logging on privileged actions
Working practice
- Named individual accounts for every engineer
- Access granted per project, revoked at exit
- Mutual NDA before discovery begins
- Code review on every change
- Pre-launch security pass on every build
- Documented breach notification path
Where you require a specific certification, penetration test or compliance framework, raise it during scoping. We will tell you plainly whether we hold it, can arrange it through a specialist, or cannot. We do not claim certifications we do not hold.
What arrives
at go-live.
Handover is a deliverable with its own acceptance criteria, not a farewell email. The test is simple: could a competent engineer who has never met us run and extend this?
- Deployment and environment runbook
- API documentation and data model diagram
- Admin and operations manual for your team
- Test cases and UAT results record
- Third-party account inventory and credential transfer
- Recorded architecture and operations walkthrough
- Signed IP assignment covering the whole build
Leaving is a supported action
There is no exit fee, no notice period on a completed build, and nothing of yours that we hold. If you want to move to an internal team or another supplier, the documentation exists precisely so that you can, and we will run paid onboarding sessions for whoever takes over.
A retainer you keep because leaving is painful is not a relationship worth having. We would rather you stayed because the next phase is worth buying.
Bring us the idea. We’ll bring back a scope you can hold us to.
A scoping call costs nothing and takes forty-five minutes. If the product does not need building yet, or needs building by someone else, we would rather say so in that call than three months into a contract.