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

Called from the build step, not a user-facing screen. Your users never open a design tool — the card is there when they deploy.

Reads the router, generates a preview per page. The generated app ships with /about and /pricing looking distinct in feeds.

Uses the app's declared color and font tokens. When the user later picks a brand, cards inherit — no manual retheme.

A build-step integration that runs before deploy.

Step 1
Add the SDK Call to Your Build
One helper in the build pipeline. It reads the app manifest, the router, and the theme tokens.
Step 2
Emit One Card Per Route
Cards land in the deploy output alongside index.html, with og:image already wired in the head.
Step 3
Iterate When the User Iterates
Redeploy triggers regeneration. New route, new card. Removed route, cleaned up.

Build-time integration, per-deploy pricing, zero end-user friction.

Why not just ship a single default OG for every app?

Because every app on your platform then has the same preview, which is worse than no preview. Unique cards per route are the point.

Do our users need an Oginify account?

No. Your platform holds the integration key. End users see a share card, not a signup flow.

How is this priced for platform-scale volume?

Bundled per deploy, quoted against your monthly deploy count. Pay-as-you-go rates aren't the right shape for you — email us.

What if a user wants to customize a specific card?

Expose the Oginify prompt as an optional field in your app builder. Advanced users tweak; everyone else keeps the default.

Are Lovable, v0 and Bolt already integrated?

Integrations are in progress with named platforms — ping us and we'll share the current status and roadmap.

One SDK call in the build step, one card per route, priced against deploys instead of humans.