Who owns the code DriftLess generates?
Handoff output is yours to deploy: GitHub repositories you control or zip exports from your runs—not a vague “platform owns everything” story.
DriftLess is a workshop: Brain scopes work, Writer edits real project files, Reviewer checks output, and you decide when to hand a version off.
When you use Send to GitHub, commits land in a repository tied to your GitHub identity (including repos DriftLess can create on your behalf when nothing is linked yet). When you use Download files, you get a zip derived from stored run artifacts for that build.
DriftLess does not position itself as your long-term production host. Shareable preview URLs exist so stakeholders can review a checked build; customer-facing traffic on your own domain runs from the host you choose after export.
Where the legal details live
Treat the Terms of Service as the contract of record for intellectual property, acceptable use, and limitations. This FAQ summarizes product behavior and is not legal advice.
Last reviewed: 2026-05-11