Most Cavuno boards use the managed frontend and visual builder. When the job board needs to live inside an existing publication, SaaS product, membership community, or custom application, the new SDK gives developers the same Cavuno backend without prescribing the frontend.
One typed client for the whole board
- Complete public surface: jobs and search, companies, salaries, blog, candidate accounts, saved jobs, alerts, applications, messaging, employer self-service, checkout, and paywalls all live under
@cavuno/board - Safe in frontend code: a publishable
pk_…key identifies the board without exposing an operator secret. Candidate and employer sessions use board-user tokens on top - Typed from the API contract: request inputs, response data, pagination, and errors stay aligned with the Board API instead of being maintained by hand
- Runs where your frontend runs: the zero-dependency client works in browsers, Node.js 20+, and Cloudflare Workers, with framework cache options passed through to
fetch
Bring your own framework
- Framework guides: production patterns for Next.js, TanStack Start, React Router, and Astro, plus Cloudflare Workers deployment guidance
- SEO infrastructure: helpers and guides cover canonical routes, metadata, structured data, redirects, and sitemap generation
- No data migration: hosted and custom frontends use the same Cavuno data, so a board can move between them without rebuilding jobs, accounts, or billing state
- SDK settings: copy the public-safe key from Settings → Developer → SDK and register the production frontend URL so verification, password-reset, magic-link, and OAuth redirects return to the custom site
Build with an agent
The package ships version-matched Agent Skills for Codex, Claude Code, Cursor, and other compatible coding agents. Run npx @cavuno/board setup, then the agent gets the correct client setup, authentication, pagination, gating, and smoke-test guidance for the installed SDK version.
Before launch, npx @cavuno/board doctor --frontend https://jobs.example.com checks board resolution, live routes, job links, JobPosting structured data, the sitemap, and robots.txt. It exits non-zero when a required check fails, so the same verification can gate deployment.
See what you can build with the Cavuno SDK, start with the SDK guide, or browse the complete SDK reference.

