Works on any stack
Next.js, React, Vue, SvelteKit, Astro, WordPress, Webflow, or plain HTML.
One script tag or an npm package. Your framework, router and build stay untouched.

A Wolfigs product
Add one line of script to the site you already ship. Your team clicks a heading and types. Works on any stack, needs no access to your code, and runs wherever you host.
No rebuild. No redeploy. No CMS to move to.
The platform your team already knows, now with the copy your marketer wanted this morning.
Works with what you already use
The trade you make today
Webnak removes that trade. The developer keeps their exact stack. The marketer stops waiting.
How it works
Drop the script tag into your layout, or install the npm package. Nothing about your build changes.
Open your own site, sign in, click a heading and type. Replace an image, fix a link, adjust spacing.
Changes save as drafts. Publishing writes a versioned revision that goes live in seconds, reversible in one click.
<script src="https://cdn.wolfigs.com/webnak.js" data-site="wnk_live_8f3c21"></script>Prefer a package? Install it with npm and the connector behaves the same. The site key is public and read only.
What you get
Next.js, React, Vue, SvelteKit, Astro, WordPress, Webflow, or plain HTML.
One script tag or an npm package. Your framework, router and build stay untouched.
Webnak never sees your repository.
It runs in the browser, on the page you already ship.
Vercel, Netlify, Cloudflare, a WordPress host, your own server.
Webnak does not host your site and does not want to.
Every publish is a revision you can roll back.
History is append-only. Restoring an old version publishes it as a new one.
Ship new code without losing content.
Each edit binds to its element by several independent signals, and a background checker re-anchors them when the page changes.
Visitors get your page, not an editor.
One cacheable JSON manifest per page, applied before paint. No layout shift.
Invite teammates with the access they need.
Optionally require approval before a change goes live.
More than text: swap an image, fix alt text, tune spacing.
Editing is content, not markup. Injected HTML and event handlers never pass the allowlist.
Review a change before anyone else sees it.
Share a preview link, keep the live page exactly as it is.
Straight answers
No. Webnak has no access to your repository, your build, or your server. It runs in the browser on the page you already publish.
Visitors fetch one cacheable JSON manifest for the page, applied before paint. No editor code is shipped to visitors and there is no layout shift.
Edits are anchored by several independent signals, not one brittle selector. A background checker re-anchors them after a change and flags anything ambiguous for review.
No. Keep your stack, your components, your host, your deploy pipeline. Publishing content never touches a build.
Yes. Every publish is a revision. Restore is one click, and the restore itself is recorded as a new revision.
Placeholder quotes
These quotes are placeholders and will be replaced with attributed customer quotes.
Copy changes used to sit in a sprint queue. Now the person who wrote the line is the person who ships it.
I kept my Next.js app exactly as it was. No CMS, no adapters, no content models to maintain.
Review before publish was the part that sold my team. Nothing goes live unseen.
Pricing
Numbers below are placeholders while pricing is finalised.
$29/ month
Placeholder pricing.
$99/ month
Placeholder pricing.