Integrations / Custom stack
Any stack: Next.js, Rails, static HTML, or internal portals.
If it serves HTML or SPA shells, you can install SentientWeb with one origin, one install key, and deterministic rules.
Custom stacks are the default for many teams. Drop the loader on the document shell, behind your feature flag or consent banner, and route production versus staging with separate keys.
For SPAs, mount after hydration or lazy-load on intent so Core Web Vitals stay healthy. Server components and edge workers can inject the tag once per layout while your deployment pipeline stays in control.
- Framework-agnostic script tag; wrap with your design system if needed.
- Environment-specific keys for staging and production.
- Talk to us for CSP, nonce, and third-party cookie policies.