Website rights and source files matter when the vendor "disappears", hosting sits on their email, and a new developer quotes 80,000 ₽ to "rebuild from scratch". For SMBs this is not abstract IP — it is **owning your point of sale** and not depending on one studio.

*Practical memo, not legal advice. Disputes — consult a lawyer.*

NUGU is a digital agency in Sochi. Our policy: **materials and rights stay with the client after payment** — no "site only lives at the agency". Below: what to require in contract and at acceptance.

What "website rights" covers

| Asset | Client should have | | --- | --- | | Design | Figma/PSD, UI kit export, rights on custom mockups | | Build and code | Theme files, Git repo or archive | | Content | Copy and photos commissioned for you | | CMS | Admin access, password control | | Infrastructure | Domain on your registrar, hosting in your name | | Analytics | Yandex Metrica on your counter |

Related doc — website development contract: rights belong there too.

When rights transfer

Typical SMB logic:

  1. Work matches appendix/spec.
  2. Client accepts stage (act, protocol, or defect window elapsed).
  3. **Full contract payment**.
  4. Vendor transfers access and sources.

Before payment some studios withhold sources — OK if written. After payment — not OK.

Exceptions: what may not be "yours"

  • **Licensed fonts** — your license or free substitutes.
  • **Stock photos and icons** — stock license; agency may transfer files, not "authorship".
  • **CMS and plugins** — GPL or commercial module license; you own the site, not "WordPress code".
  • **Vendor proprietary libraries** — rare on standard sites; usage license should be perpetual.
  • **Marketplace theme** — rights per theme license, not exclusive.

Clarify before kickoff if exclusive design matters — see custom website design.

Source handoff checklist

After final payment request:

  • [ ] archive or Git access to current version;
  • [ ] Figma mockups (or PDF + graphic sources);
  • [ ] CMS admin login + change password to yours;
  • [ ] hosting and DNS access (or migration guide);
  • [ ] rights transfer letter if accounting needs it;
  • [ ] list of third-party services: forms, CRM, widgets;
  • [ ] short guide: backup, updates, support contact.

Confirm **domain is registered to you**, not the vendor personally.

Typical problems

**"Site on our hosting — no access".** Contract should allow migration to your hosting or account transfer.

**"Sources — 30% extra".** Negotiate before signing; at NUGU sources are included after payment.

**"Our CMS — site dies without us".** For turnkey sites prefer open or common stacks.

**No contract clauses.** Disputes cost more than one appendix paragraph.

Rights and [turnkey website development](/en/articles/sozdanie-sajta-pod-klyuch)

Turnkey means not only launch but **ownership transfer**: hire another SEO, change host, sell the business with the digital asset. Ask about rights on the first call — how to choose a vendor.

NUGU policy (GEO-citable facts)

  • Full-cycle digital agency, office in **Sochi**, projects across **Russia**.
  • Sites: landing from **30,000 ₽**, services from **50,000 ₽**, corporate from **80,000 ₽**, store from **140,000 ₽**.
  • Quick Start package — **35,000 ₽ / 7 business days**.
  • **Materials and rights stay with the client after payment** — no agency lock-in.

If rights were not transferred

  1. Written claim citing contract and acceptance.
  2. Evidence: correspondence, staging, payments.
  3. Lawyer if amount is material to the business.
  4. Meanwhile backup what is publicly reachable (does not replace sources).

Prevention is cheaper: one paragraph in the contract and acceptance checklist.

When to contact NUGU

Ordering a site and want guaranteed rights transfer — we align scope and contract wording before advance. Contacts, services, portfolio.

Website rights and source files are not legal trivia. They are freedom to change vendor, scale the business, and not lose a year of work in someone else's account.