Give Every Generated App a Real OG Card at Build Time
Bake Oginify into Lovable, v0, Bolt or Cursor build outputs so every app your users deploy carries a share card by default.
For Platforms Shipping Someone Else's App
Runs Inside the Build
Called from the build step, not a user-facing screen. Your users never open a design tool — the card is there when they deploy.
One Card Per Route, Automatically
Reads the router, generates a preview per page. The generated app ships with /about and /pricing looking distinct in feeds.
Neutral by Default, Themable by User
Uses the app's declared color and font tokens. When the user later picks a brand, cards inherit — no manual retheme.
Explore Other Audiences
For Indie Hackers & Solo BuildersFor Agencies & SEO ConsultantsFor CMS Platforms
Frequently Asked Questions
Embedding OG-image generation into platforms like Lovable, Bolt, v0 and Cursor-hosted projects.
How do I embed OG-image generation into a no-code or AI-coding platform?
Wire the Oginify API into the platform's publish or deploy step: on each user publish, POST the resulting URL, receive four CDN card URLs, and inject the top one into the deployed page's <head> automatically. End users get per-page OG cards without a design step.
Does Lovable, Bolt, v0, Framer or Webflow support Oginify natively?
Any platform that lets users edit <head> or exposes a build hook can integrate — that includes Lovable, Bolt, v0, Framer, Webflow, Cursor and the major static-site builders. Native integrations exist for a subset; the API works for the rest with a ~50-line handler.
Who pays for the OG-image generation — the platform or the end user?
Platform integrations typically use the dedicated-tenant plan billed monthly to the platform, with generation quota pooled across all end users. The platform decides whether to bundle it into a paid tier or expose the cost — Oginify only bills the platform, not the platform's users.
Can the generated cards match each end user's brand automatically?
Yes — the API accepts per-request color and logo overrides. If the platform already knows a user's brand colors and logo (most no-code builders do), pass them in the API call and the generated cards match without a per-user configuration step.
What's the API latency and how does it affect platform publish times?
The generate endpoint returns a job id in ~200ms; the four CDN URLs become 200 OK in ~15–30 seconds. Most platform integrations kick off generation at publish start and inject the top URL by the time deployment finishes, so end users see no perceived slowdown.
Can platforms white-label Oginify so 'Oginify' doesn't appear in end-user UI?
Yes, on the dedicated-tenant plan. The pipeline runs under the platform's own subdomain and neither the CDN URLs nor the generated images carry Oginify branding. End users see 'made with <YourPlatform>' or no attribution — the platform chooses.
Ship every user's app with a share card baked in
One SDK call in the build step, one card per route, priced against deploys instead of humans.