For Developers
One package. Every backend feature your Next.js site needs.
One npm install. 22 modules. 100+ components. The complete Next.js backend, out of the box.
The Problem
8 services. 8 dashboards. 8 bills.
Every feature you add means another SDK, another vendor, another integration to maintain.
One SDK per feature. Analytics, SEO, forms, CRM, commerce, reviews, scheduling, messaging, projects, and a website CMS, each with its own package and keys.
One import instead. Every module ships in @sonordev/site-kit, typed, so the whole backend is one dependency.
import { ... } from '@sonordev/site-kit'- 1
- npm install
- 22
- Integrated modules
- 100+
- Typed components
- 22
- AI skills
@sonordev/site-kit
Listen · Act · Earn · Speak
Server & client
via Signal
How It Works
One import. One API. 22 modules + Signal AI. Your Next.js app talks to Sonor. Sonor handles the rest.
site-kit in your app. Components and hooks call the Sonor API for you. No custom backend, no glue code.
Modules behind one API. SEO, analytics, forms, CRM, commerce, blog, popups, sync, reputation, broadcast, images, and redirects share one record.
Signal on top. Echo, 22 AI skills, and the knowledge graph work from the same data your site writes.
Code Examples
Import. Configure. Ship. Server or client: site-kit adapts to your architecture.
import { getManagedMetadata } from '@sonordev/site-kit/seo/server'import { ManagedSchema } from '@sonordev/site-kit/seo/server' export async function generateMetadata() { return await getManagedMetadata()} export default function RootLayout({ children }) { return ( <html> <head> <ManagedSchema /> </head> <body>{children}</body> </html> )}Server vs Client
RSC-first. Client when you need it. SEO, Blog, and Images run on the server. Analytics, chat, popups, and Signal run in the browser.
Server (RSC): SEO, Blog, Images. getManagedMetadata, ManagedSchema, Article, ManagedImage: all run at render time for optimal SEO and performance.
Client: Analytics, chat, popups, Signal. AnalyticsProvider, EngageWidget, SignalBridge hydrate on the client for tracking, chat, popups, and A/B experiments.
CLI
From zero to full-stack in 3 minutes.
One command. Sonor scans your project, installs site-kit, configures every module.
init. Detects your Next.js project, installs site-kit, configures analytics, SEO, forms, and chat, and connects to api.sonor.io.
scan. Registers every page with Sonor and generates the sitemap, robots.txt, and llms.txt.
setup. Signal AI optimizes metadata, generates FAQ content, and creates schema markup for every page.
For coding agents
Docs your agent can follow.
Tell it this project uses Sonor and point it at sonor.dev. The agent wires your site to the same contract every Sonor site follows, then verifies it, without anyone memorizing how Sonor does forms, SEO or analytics.
Markdown at every URL. Add .md to any sonor.dev page and the agent reads the clean source, not the HTML around it.
llms.txt and llms-full.txt. The whole documentation set as an index, or as one file.
An MCP server. search_docs and get_doc at sonor.dev/api/mcp, so the agent looks it up instead of guessing.
A CLI that answers in JSON. Every sonor-setup command takes --json, so the agent can scaffold, sync and verify on its own.
This project uses Sonor. Follow sonor.dev.- Any page as Markdown
- sonor.dev/<page>.md
- Every page, one file
- sonor.dev/llms.txt
- MCP server
- sonor.dev/api/mcp
- Wire it, then prove it
- npx sonor-setup verify --json
Ready to ship faster?
One package. One API. Every backend feature. Starting at $99/mo.
See what you'll pay
One platform, transparent pricing. Every module included from $99/mo.
Pricing details