KASTRICK / PROJECT FAQ
Questions worth answering before the build starts.
Scope, ownership, data, maintenance and third-party services are easier to work with when the expectations are visible before a proposal is signed. These answers summarize the current Kastrick service model; the applicable written agreement remains authoritative.
STARTING
01
Do I need a complete specification before contacting Kastrick?
No. A useful request starts with the real problem, what already exists, the outcome you want, references, timing and any constraints you already know. Kastrick can use that context to identify follow-up questions before scope is agreed.
STARTING
02
What kinds of projects can Kastrick take on?
Depending on the agreed scope, Kastrick works on custom websites, web applications, backend software, REST APIs, databases, business email configuration, DNS/domain routing, deployment, cloud infrastructure, migrations, security hardening, performance work, maintenance and technical consulting.
SCOPE + PAYMENT
03
How is the project scope decided?
The applicable quotation, proposal, invoice, statement of work or other written agreement defines the project scope. New pages, integrations, redesigns, API endpoints or other changes outside that scope can be treated as additional work.
SCOPE + PAYMENT
04
How is pricing determined?
Project pricing is determined individually from the scope, complexity, estimated engineering effort, infrastructure requirements and requested services. Unless otherwise agreed, a deposit is required before work begins and the remaining balance is due before final delivery, deployment or transfer of administrative control.
SCOPE + PAYMENT
05
Are future features automatically included in the original price?
No. Future feature development, redesigns, migrations and ongoing maintenance are not automatically included unless the written agreement says otherwise. Additional work is priced or quoted before it begins.
OWNERSHIP + DATA
06
Do I own the custom work created for my project?
Subject to full payment and the applicable agreement, the Terms provide for ownership of custom deliverables created specifically for the project, such as project-specific frontend designs, backend code, APIs, database schemas, UI/UX assets, graphics and project documentation where applicable.
OWNERSHIP + DATA
07
What does Kastrick keep?
Kastrick keeps ownership of its pre-existing reusable technology: frameworks, libraries, deployment systems, templates, internal tools, automation, security mechanisms, workflows, methodologies and other reusable engineering components. Third-party and open-source components remain governed by their own licenses.
OWNERSHIP + DATA
08
Who owns the data in a managed backend or database?
Client Data remains the property of the Client. Where Kastrick provides backend infrastructure, hosting or database management, the Terms describe Kastrick as a technical service provider processing that data on the Client's behalf.
AFTER LAUNCH
09
Can Kastrick keep maintaining the project after launch?
Yes, when there is an ongoing maintenance arrangement, available Maintenance Deposit or another approved scope. Maintenance can include troubleshooting, security updates, performance improvements, backup verification, SSL, email service maintenance, database optimization and other agreed work.
AFTER LAUNCH
10
What happens if a delivered feature has a Kastrick implementation bug?
If a software defect directly results from a Kastrick implementation error within the originally agreed scope, the Terms state that Kastrick will correct that issue without additional charge. This does not include later requested modifications or expanded scope.
AFTER LAUNCH
11
Who pays for third-party hosting, domains, email providers or external APIs?
Unless a written agreement says otherwise, fees charged by independent third-party providers remain the Client's responsibility. Kastrick is also not responsible for outages, pricing changes or policy changes caused by those independent providers.
Need an answer about a specific build? The FAQ cannot define a project-specific promise. Send the actual context through the request flow and Kastrick can scope the question against that project.
Open the project request →