Portfolio management without vendor lock-in.
Govern tattoo portfolio intake, artist ownership, review, portability, and distribution across Studio OS, Artist OS, websites, partner tools, and tattoo.co.
The problem
What breaks today
Tattoo portfolios are spread across phones, Instagram, studio websites, old CMS projects, CRMs, and agency folders. When the studio changes tools, the portfolio graph, attribution, inquiry history, and review workflow usually break.
tattoo.dev developer surface
The official TattooAPI docs and builder resources
TattooAPI turns approved work into governed creative proof objects with attribution, rights, review state, source history, and distribution rules that can move across websites, marketplaces, Studio OS, Artist OS, and growth-operator workflows.
Use tattoo.dev as the official TattooAPI developer surface: learn the primitives, read the API references, understand auth and review boundaries, then request access for the product surface you are building.
Next step
Keep the website flexible. Keep the data governed.
Studio OS, Artist OS, agency-built websites, and builder integrations should all compose around TattooAPI projections instead of raw source systems.