Lamina vs uselamina.ai (https://lamina.dev/learn/compare/lamina-vs-uselamina-ai): Lamina at lamina.dev is an Apache-2.0 open-source transactional product graph and agent workflow for AI coding agents. It writes validated graph knowledge to the local product graph and verifies live builds with /lamina-verify. uselamina.ai is a separate commercial product: a creative API for media generation. They are not affiliated, share no codebase, and serve different purposes. If search results confused you, you want lamina.dev when you need product behavior design for Cursor or Claude Code workflows. You want uselamina.ai when you need generated media assets via API. Wrong installs happen when developers assume the shared name implies the same product. Lamina (lamina.dev) is an open-source transactional product graph and agent workflow. Its CLI and portable skills publish validated GraphVersions, produce query projections, and verify live builds with independent Persona Missions and runtime evidence. It is not a UI tool, headless CMS, app builder, or uselamina.ai. Compare uselamina.ai to Lamina when you need durable product knowledge in a local graph, not just generated UI or ephemeral planning. Full guide: https://lamina.dev/learn/compare/lamina-vs-uselamina-ai.

Lamina vs uselamina.ai

Lamina at lamina.dev is an open-source transactional product graph and agent workflow for AI coding agents. uselamina.ai is a creative API for media generation. Different products, no affiliation.

Curated by Aryan Iyappan · Updated 2026-07-27

Not affiliated with uselamina.ai. lamina.dev is product behavior design for AI agents; uselamina.ai is a media API.

You are in the right place if

You found the wrong Lamina in search results.
You expected a media API but landed on lamina.dev.
You want to confirm there is no affiliation before installing.
FAQ uselamina-disambiguation sent you here.

Context

Entity disambiguation page. Short by design: the risk is wrong product selection, not feature comparison. Verify the domain before you install or integrate.

Common situations

Concrete cases from AI-shipping workflows. Each shows what the alternative handles and where validated graph knowledge and verification evidence help.

Searched Lamina API for image generation

Situation: You need programmatic media generation for a creative tool.
What uselamina.ai does: uselamina.ai provides media generation API.
What Lamina adds: Wrong product. Use uselamina.ai for media, not lamina.dev.
Takeaway: Check domain: lamina.dev is behavior design for agents.

Need validated graph knowledge for booking app

Situation: You ship with Cursor and need checkout hold rules specced.
What uselamina.ai does: uselamina.ai does not do product behavior design.
What Lamina adds: lamina.dev: /lamina-init, /lamina-design, /lamina-verify.
Takeaway: Product behavior: lamina.dev.

Evaluating both names for a startup stack

Situation: Media pipeline plus AI-built application in same company.
What uselamina.ai does: uselamina.ai for creative API if that fits media needs.
What Lamina adds: lamina.dev for agent behavior layer in app repo. No integration between them.
Takeaway: Unrelated products; name collision only.

Comparison

lamina.dev vs uselamina.ai
Dimension	uselamina.ai	Lamina
Primary job	Media generation API	Product behavior design for agents
Layer in stack	Creative / media API	Transactional product graph + agent workflow
Primary output	Generated media assets	Validated GraphVersion plus query projections
Writes app source?	No	No
Behavior spec (states, flows, permissions)	Not applicable	Core purpose
Durable in-repo artifact	API responses and assets	Validated GraphVersion plus query projections
Post-build verification	Not applicable	Independent Persona Missions with runtime evidence
Repo and stack fit	API consumers	CLI plus portable skills in any repo and stack
Best when	Media generation use cases	Spec app behavior with agents
When you don't need Lamina	You need media API	Wrong product: use lamina.dev instead
Compose with Lamina?	Not applicable	Install from lamina.dev docs

Frequently asked questions

Are they affiliated?

No. Different products, codebases, and purposes.

Why do they share a name?

Independent naming collision. Always verify domain: lamina.dev for this skill.

I installed the wrong one. What now?

Uninstall or cancel the media API integration. Install Lamina from lamina.dev docs for agent behavior design.

Comparisons map stack layers, durable outputs, and provenance-marked legacy examples. Updated when major tools change positioning.

Install Lamina with your agent.

Copy the repository-matched prompt. Your agent installs the standalone CLI, adds every Lamina skill for your active agent, configures supported passive rules, checks the setup, and tells you when to start a fresh session with /lamina-init.

Skills work across coding agents. Passive setup currently supports Codex, Claude Code, and Cursor.