Code ownership
Source code and documentation transfer to you. We keep no hidden dependency and no license trap.
Six Commitments
Each one is part of the service agreement, not a marketing promise.
Fixed milestones
Scope, deliverables, and acceptance criteria are written before work starts. Payment follows delivery.
30-day warranty
Bugs found in delivered functionality are fixed at no cost for 30 days after acceptance.
NDA and confidentiality
We sign your NDA before access to code, data, or infrastructure. Client names stay private by default.
Transparent reporting
A shared task board, weekly progress notes, and a direct channel to the engineer doing the work.
No vendor lock-in
Code follows standard practices, with documentation and deployment scripts you can hand to another team.
What Is Covered
The warranty is specific. It does not replace a support contract.
Covered for 30 days
- Defects in delivered functionality
- Mismatch between the agreed scope and the result
- Bugs caused by our code or configuration
- Security issues introduced by our changes
- Deployment and setup errors on the target environment
Not covered
- New features and scope changes
- Third-party plugin or API changes
- Hosting, DNS, or server failures outside our control
- Content edits made by the client
- Issues caused by unapproved code changes by others
How a Guarantee Works
From signature to the last fix, every step has a written record.
-
Scope and agreement
We describe deliverables, acceptance criteria, and payment milestones. You approve them in writing.
-
Access and NDA
We sign your NDA and a service agreement, then receive access to the repository, staging, and the systems we need.
-
Delivery and acceptance
You test against the agreed criteria. We fix what does not match before the milestone is closed.
-
Warranty and handover
The 30-day warranty starts at acceptance. We hand over code, documentation, and deployment notes.
Questions & Answers
The details clients ask about most.
Is the warranty really free?
Yes, for defects in what we delivered. If the cause is a new requirement or a change by another team, we estimate the fix separately.
Who owns the code?
You do, after the final payment for the milestone. Third-party libraries keep their own licenses, and we list them in the handover.
Can you sign our NDA?
Yes. We review and sign a mutual NDA before any technical access. If you have a standard DPA, we review that too.
What if we stop the project early?
You pay for completed and accepted milestones. Work in progress is handed over with the code and notes.
Do you provide support after the warranty?
Yes, under a monthly retainer or a separate support agreement. Response times are agreed in advance.