Install it the way your stack already works
The widget is one <script> tag on any site, on any stack. If we have an
SDK for yours, take that instead — it wires up signed identity and error
reporting for you, which is the part that is fiddly to do by hand.
Plain HTML
Works anywhere. Paste it before </body> and you are done.
html
<script async src="https://vroxy.ai/widget.js?tenant=YOUR_PUBLIC_KEY"></script>
Ruby on Rails
The vroxy gem injects the snippet on every HTML response, signs
identify() claims from current_user automatically, and forwards your
app’s exceptions as client errors. This site runs it — we use our own gem
on our own marketing pages.
Node — Express and Next.js
Middleware for Express and Next.js with the same three jobs: inject, sign, report. Signing happens on your server, so the secret never reaches the browser.
Python — Django and Flask
Middleware for Django and Flask, matching the Ruby gem feature for feature.
WordPress
A plugin. Paste your public key in the settings screen and identity is signed from the logged-in WordPress user — including on cached pages, which is where naive implementations usually break.
Direct API
Anything not on that list talks to the REST API: full CRUD over your
knowledge base, a stateless bot/reply round-trip for your own harness, and
glossary sync so a build step can push your app’s vocabulary straight in.
Authentication is a workspace-scoped bearer token with explicit read or write scope.