Best-of-breed services, one control plane.
Every DevSewa product is scoped to the same application — a tenant with a test and a live environment. Turn on one product or all of them; the key, the policy and the audit trail stay the same.
Products
Available today, and open in preview
Auth, Mail, Vault and Secrets are in production for DevSewa customers. SMS, Billing, Hosting and Backups are built on engines that already run other products on the fleet and open to early-access customers on request.
Authentication
Hosted sign-in, MFA and sessions
- 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
Transactional Mail
Codes, receipts and notices from your own domain
- Sender domain and alias per application
- Published templates with server-side variable substitution
- Send a test from the console before you wire anything
User Vault
Encrypted per-user files through a backend-only boundary
- Isolation by (application, tenant, end-user)
- Completed server-to-server upload and download routes
- One-time vault capabilities consumed inside Authority Core
Secret Store
Per-application environment your backend reads at runtime
- Environment-variable-shaped names, encrypted values
- Encrypted with a key dedicated to customer secrets
- Reveal only via the owning backend’s client secret
SMS
OTP and notifications from your own provider account
- Your own provider account per application: SMS Nepal, Twilio and more
- Routing by country prefix with a primary provider and optional fallback
- OTP send and verify with per-tenant rate budgets
Billing
Your GPSewa merchant account, connected read-only
- Connect with your GPSewa sign-in; DevSewa never sees your GPSewa password
- Per-tenant overview: customers, subscriptions, open and paid invoices, failed payments
- Scopes chosen on GPSewa, re-checked live on every read
Hosting
Linux VPS and dedicated servers with a browser console
- Linux VPS on KVM with cloud-init; dedicated servers with out-of-band power
- Power on, shut down, reset — with live state and uptime
- Browser VNC console (VPS) or serial-over-LAN (dedicated) via a 60-second single-use ticket
Backups
Scheduled snapshots with receipts and restore checks
- Scheduled jobs per application with retention you can see
- Run on demand and follow the run to a receipt
- Receipts carry snapshot id, size, duration and a redacted error if any
Logs
Ship your application logs, search them per environment
- One call to ship an event or a batch of up to 500
- Severity, source, server and time filters; full-text search
- Cursor pagination that never skips or repeats
Shared foundation
What every product inherits from the platform.
A product call is always for one application. The client secret or the console session decides which; a request body never can.
Both environments exist for a tenant from day one, with their own keys and policy, so nothing has to be renamed to go live.
Creates, updates, key mints, sends, grants and deletes are all recorded with actor, action and time.
When an engine is unreachable you get a 502 you can retry — never a silent fallback to another tenant’s configuration.
Cross-tenant access is 403. A resource you must not know about answers the same 404 as one that does not exist.
The console and this site are stateless. Engine credentials are materialised only into the authority core at deploy time.
Start with the product you need first.
Most teams begin with Auth and add Mail the same day. Vault and Secrets are there when you need them.