Rights that match the work.

NORA helps buyers understand what they can do with finished software—and helps creators protect the work they made. Every code listing names its licence before purchase.

Reusable code

Choose the scope you actually need.

Use on one live project. No resale or redistribution.

Single project

Best forA founder, a business, or one end-client build.

Allowed: Deploy in one named commercial or personal production application.
Not allowed: Reuse across separate client projects or sell the source as its own product.

Reuse in client work. Keep the source private.

Agency

Best forFreelancers, studios, and small teams shipping repeatedly.

Allowed: Use across the purchaser's internal products and client projects, when the record offers this tier.
Not allowed: Publish the source, list it on a competing marketplace, or bundle it as an uncompiled template kit.

For broader rights, unusual delivery, or support needs.

Custom terms

Best forLarger teams, white-label products, and non-standard use cases.

Allowed: Whatever the buyer and creator agree in writing before acquisition.
Not allowed: Assume rights that are not explicitly part of that agreement.

Marketplace baseline

Buy the right to use it. Not the right to resell it.

Under every NORA code tier, the original asset cannot be republished, repackaged as a standalone product, or made publicly downloadable as a substitute for the original.

Private repositories and access for collaborators who need to build, maintain, or deploy the buyer's product are permitted. A product record may grant additional rights; it never removes the baseline without saying so clearly.

Not every listing is source code

Live products and integrations use delivery terms.

Live project

Access, not ownership by default.

The record states who hosts it, whether source is included, the access period, and what happens at the end of that period.

Paid integration

A defined result, not an open-ended brief.

The record states requirements, deliverables, support window, handover, and exclusions before work begins.

Attribution & dependencies

Credit is clear. Upstream terms stay intact.

Attribution is optional unless the individual record requires it. Creators can ask for a credit link; buyers should not have to guess.

If a product includes open-source software, its upstream licence notices and obligations still apply. NORA licences only the creator's original contribution.

Need different rights?

Ask before you acquire.

Contact NORA