AvailableSign-in that belongs behind your backend.

Register an application, allow-list your callback URLs and send users to DevSewa’s hosted screens. Passwords, e-mail codes, authenticator apps and recovery are handled for you; your backend exchanges a one-time ticket for a verified identity.

callback handler · your backend
// https://app.example.com/auth/callback?ticket=…
const res = await fetch('https://auth.api.devsewa.com/v1/auth/exchange', {
  method: 'POST',
  headers: {
    authorization: `Bearer ${process.env.DEVSEWA_CLIENT_SECRET}`,
    'content-type': 'application/json',
  },
  body: JSON.stringify({ ticket }),
})
const { user } = await res.json()
// { subject, email, name } — create your own session

What you get

Authentication, without running it.

Served from auth.api.devsewa.com and managed from the console. Backed by AUTH_APP, mediated by the DevSewa control plane.

  • Hosted sign-up, sign-in, e-mail verification and password reset
  • MFA policy per application: off, optional or required
  • Client secrets minted once, stored hashed, rotated without downtime
  • Exact-match callback and origin allow-lists
  • Test and live environments per tenant
  • Every mutation written to an audit log

Isolation

How it stays yours.

Identity store
One collection per (app, tenant) in the identity engine
Callback enforcement
DevSewa redirects only to URLs you allow-listed
Policy
Enforced at the mediation layer, not just in the UI

Add Authentication to your application.

Create an account, register a test application and exchange your first ticket in under ten minutes.