Tuqo + Clerk
Clerk is turnkey authentication: sign-in, sign-up, social logins, ready-made UI components and sessions. The front end connects with the publishable key, which is public; the secret key stays on a server and is not needed for front-end auth.
What Tuqo + Clerk gives you
- Sign-in, sign-up, magic links and social logins out of the box
- Ready-made components (React/JS), minimal code
- Sessions and JWT without an auth server of your own
- User management in the Clerk dashboard
Create a Clerk application
Copy the publishable key (pk_...) from the Clerk dashboard.
Add the SDK
@clerk/clerk-js or @clerk/clerk-react, initialized with the publishable key.
Add sign-in components
Ready-made SignIn, SignUp and UserButton, or your own UI on top of the API.
Deploy to Tuqo
The site is on name.tuqo.ru, and auth works from the browser.
import { Clerk } from '@clerk/clerk-js'
// the publishable key is for the front end (public)
const clerk = new Clerk('pk_live_...')
await clerk.load()
if (clerk.user) { /* the user is signed in */ }Security
The publishable key is meant for the front end (public). The secret key stays ONLY on a server and is not needed for client-side auth. Never put it in a static site.
Tuqo serves the front end over HTTPS and never touches your data or the service's secrets.
Tuqo + Clerk — frequently asked questions
Where do I use Clerk's secret key? +
Only on a server (for example, in an edge or server function for backend operations). Only the publishable key goes into a static site.
Does it work on a plain static site (SPA)? +
Yes, Clerk is built for SPAs: sign-in and sessions are fully client-side.
Can I use a custom domain? +
Yes. Attach the domain in Tuqo (from the Start plan), then add it in the Clerk settings.