Service terms

How this works

The tiers and exclusions below are what you are buying and what you are not. The full agreement — both sides’ obligations, liability, and how a dispute is handled — is provided in writing and agreed before any work begins, and you can decline it without cost first.

1. What the service is

A fixed-scope deployment of a SvelteKit starter kit that you hold a licence for, onto infrastructure in your own accounts. The deliverable is a running deployment plus a written record of exactly what was done, how to redeploy it, and how to roll it back.

It is priced as a defined deliverable, not as an hourly rate and not as an estimate. The tier price is the entire fee for the scope below.

2. Tiers

3. Not included — at every tier, at every price

These are the boundary of the offer rather than negotiation positions. Knowing them before you buy is the point of listing them.

• Anything needing your accounts or credentials. This service does not create, own, or hold any account of yours.
• Anything that puts you on a third party’s bill. No tier purchases, pays for, or stands behind a third-party service on your behalf — no managed database plan, domain, email service, or paid CDN tier.
• Application development. Feature work, UI, business logic, and schema changes beyond the kit’s own migrations are out of scope. The service deploys the kit you licensed; the deployed application is yours from acceptance onward.
• Security hardening, penetration testing, or compliance certification. T3 hardens a deployment. It does not certify your product or make any claim about it.
• Data migration from your existing system. Moving your production data is your operation, on your plan, with your backups.
• Ongoing operations. Monitoring, incident response, patching, uptime, backups, and on-call are not part of any tier.
• Support for your own modifications. The licence already excludes this, and this service does not reopen it.
• Trained-staff handover, workshops, or live sessions. Work is delivered in writing. That is a constraint of how this service operates, not a negotiating position.

4. What you provide

• A licence for the kit being deployed. The service cannot be bought without one.
• Your own accounts on the target platform, and the access needed to work in them.
• A decision on the target platform, where the tier does not fix it.
• Data migration, if any, as your own operation — see §3.
• Timely answers to the questions the work depends on. Deployment stops at a question, and an unanswered question is the most common reason a fixed-scope job overruns.

5. Price and payment

• Payment is 100% before work begins. This is a fixed-scope, fixed-price engagement with a written deliverable, so the work is not started against an unpaid invoice.
• The tier price is the entire fee for the scope in §2 and §3. There is no hourly component and no additional charge for the work described.
• The price excludes payment-processing fees. On the $149 tier those fees are a material fraction of the total, so they are stated rather than absorbed, and they are quoted to you in writing before you pay.
• A change to the scope is a new agreement at a new price, agreed in writing before the additional work begins. See §8.

6. Acceptance

Each tier names its deliverable in §2, and each is checkable from your own side: the deployment builds, the health endpoint answers over your own domain, login and role-based access behave as documented, and the runbook describes what was done. Acceptance is the deliverable behaving as described in your accounts.

The engagement is complete when the described deliverable is demonstrated. It does not extend to the deployed application’s behaviour after that point, which is yours.

7. Support

Written questions about the specific deployment are answered while the engagement is open, and for 30 days after acceptance. This is deliberately narrow: it is support for the deployment, not ongoing operations, and not a retainer.

This is separate from your kit licence, which carries its own support window — seethe licence, which since version 1.5 includes12 months of standard support from purchase.

8. Changes to the scope

Work outside §2 and §3 is a change order: it is quoted, agreed and paid before it starts, and it does not begin by being requested. Nothing about an open engagement obliges either side to accept a change.

9. Your licence is separate, and it still applies

The End User License Agreement governs the kit and is unaffected by this page. Paying for a service grants no additional licence rights, seats, or projects.

The licence already draws this boundary, in its own words. Under “Not included”it lists “Custom development, consulting, or implementation services”. This service is that, priced separately. Under “Included” the licence grants“Installation assistance” — which remains free to every licence holder, and which this page does not sell.