DryDock Kit
Support and updates
DryDock Kit is source code you run and own. Support covers the code as shipped, by email, from the person who wrote it. It doesn't cover building, hosting or operating your product.
How to get help
Email support@drydockkit.com. Use the matching template from docs/support/request-templates.md in the download: a request with the version, the exact command and the full error is usually answered in one reply instead of three. Never send secrets: no .env, API keys, webhook secrets or database URLs with passwords.
| Developer license | Teams license | |
|---|---|---|
| Channel | Email, answered first | |
| Response target | Within 3 business days | Within 2 business days |
Response times are targets, not a service-level agreement. Support is in English.
What support covers
- Installing and running the product as documented.
- Configuring the environment, database, email, and Stripe, Razorpay, Paddle or Polar as the docs describe.
- Deploying with the documented paths: Docker on a VPS, with nginx or CloudPanel in front.
- Bugs in the code as shipped.
- Questions about how a subsystem works, or where a change belongs.
What it doesn't cover
- Designing or writing your product's features, or reviewing your changes.
- Debugging code you or an AI assistant added or changed.
- Hosting, servers, DNS, TLS, email deliverability, or your payment provider accounts.
- Deployment targets the docs don't cover, such as Vercel, Kubernetes or serverless.
- Legal, tax or compliance advice.
Custom development may be available separately. Ask at the same address.
Updates
Your license includes every 1.x release: new minor versions (1.1, 1.2, …) and patches. A future 2.0, if there is one, may be a paid upgrade. You keep every version you've received.
Updates bring security fixes, bug fixes, dependency and framework upgrades, and documentation. When a release is published, every buyer is emailed a link to the new ZIP at the address they bought with. If you can't find it, email support@drydockkit.com with your order ID. UPGRADING.md shows how to merge a release into code you've changed. There's no fixed schedule; the changelog is the record of what shipped and when.
Bugs, features and security issues
Report a bug on an unmodified copy of the latest 1.x release if you can, or say what you changed. Confirmed bugs are fixed in a later release; no date is promised. Feature requests are welcome and shape the roadmap, but they aren't commitments. Report a suspected vulnerability privately, with “SECURITY” in the subject.