HawkeForge
← All posts
Guide·3 min read

Can you actually sell AI-generated game assets?

The licensing question every developer quietly worries about — what the law does and doesn't give you, what most tools' fine print hides, and how HawkeForge handles it.

By Patrick

Ask this question on any gamedev forum and you'll get thirty confident answers that contradict each other. Here's the honest version, as plainly as we can put it. (Obligatory and genuine: this is not legal advice — for decisions that matter to your business, talk to a lawyer.)

The uncomfortable truth about copyright

In the United States, the Copyright Office's current position is that purely AI-generated output — no meaningful human authorship — is not copyrightable by anyone. Not by you, not by the tool vendor. So when any AI platform says "you own your generations," it's worth asking what "own" means for a work that may have no copyright attached at all.

What actually protects you in practice is contract: what the platform's terms promise you, what they promise not to do with your output, and what rights they quietly keep. That's where the fine print starts to matter.

The fine print patterns to watch for

Across the AI-asset market you'll find, with some regularity:

None of this makes those tools bad. It makes not reading the terms bad.

How HawkeForge handles it

We took a position and put it in the terms rather than the marketing copy:

Free tier: public by design. Free generations appear in our public gallery and we can showcase them. You keep a license to use what you made — but if you're shipping something commercial, free-tier output is the wrong tool, on any platform.

Paid plans: private and assigned to you. Your generations are private — no gallery, no training on your outputs, no re-licensing to anyone else. We contractually assign you everything assignable in the output and commit that HawkeForge claims nothing in it. Since copyright in pure AI output is shaky ground for everyone, we protect you the reliable way: by contract, with your prompts and results kept private so there's nothing for anyone else to copy in the first place.

A license-clean pipeline underneath. We chose and, where necessary, rebuilt our generation stack around commercially clean components, and the platform tracks license status per asset rather than hand-waving it at the account level. When an asset would carry strings, we'd rather block it than surprise you in a due-diligence call.

The checklist we'd apply to any tool (including us)

  1. Does the free tier require attribution? Would you remember to include it?
  2. Can the platform train on, publish, or re-license your generations?
  3. Does the tool disclose the licenses of the models underneath it?
  4. Is "commercial use" defined in the terms, or only claimed on the pricing page?
  5. If you cancel, what happens to your rights in already-exported assets? (Ours: you keep everything you exported.)

If a vendor's answers are hard to find, that's an answer too.

Read our full terms — or start on the free tier and see the per-asset license status in the app itself.