One login, kept in good order.
Your organization has a front door now — the login page. DeveloperOffice SSO is that door, properly built: hosted single sign-on on standard OpenID Connect, one flat rate, and a ledger of every entry.
The idea
Sign-in is a record, not a metric.
Think about what a login actually is.
It is the moment your organization decides who someone is. It happens quietly, thousands of times, and the ten-thousandth time matters exactly as much as the first. That makes identity a record-keeping problem — the kind registries and banks solved on paper long before software existed.
The prevailing model in this industry treats it as a growth metric instead: count the monthly active users, bill the count. The price of your own front door climbs with your success, and every good quarter arrives with a small tax payable to your login vendor.
We built the opposite, on purpose. One flat rate, capped by headcount. An append-only audit ledger, because entries through your door deserve a permanent record. Vanilla Postgres underneath, and a full export of your tenant’s data on request — a record you cannot take with you was never really yours.
That is the whole idea. Everything below is evidence.
Protocol
Standards do the talking.
DeveloperOffice SSO implements OAuth 2.0 and OpenID Connect with PKCE. ID tokens are signed with ES256 and verified against a public JWKS — verifying our tokens needs no shared secret, so there is none to distribute and none to leak. An identity provider should be verifiable before you sign a thing. Ours is: the excerpt below is served live from this domain.
Rendered from the live endpoint at page load — not a screenshot. Point any standard OIDC client library at it and it configures itself.
Controls
Everything an identity office needs.
Multi-factor sign-in
Time-based codes and passkeys, enforced by your organization’s login policy.
The audit ledger
Append-only. Every sign-in, grant and administrative action, on the record.
Directory sync
SCIM keeps your user directory and ours in step, joiners and leavers alike.
Hierarchy and grants
Organization → project → application. Grant another organization’s users access to a project without duplicating anything.
Your letterhead
The hosted login page carries your name and your color, and speaks three languages:
Sign in · පිවිසෙන්න · உள்நுழையவும்
Assisted configuration
Describe the change in plain words; the console co-pilot drafts it. You approve. (See 06.)
In service
We use the same product we sell.
That register is the whole of it today. We would rather show you a short true list than a wall of borrowed logos.
The questions
Asked every time. Answered in writing.
What happens to our bill when we grow?
Nothing sudden. Every tier is a flat monthly rate capped by headcount — never per monthly active user. A good quarter changes your revenue, not your identity invoice. Sri Lankan organizations are invoiced in Rupees, at an indicative local price.
What happens if we ever want to leave?
You leave with everything. The platform runs on vanilla Postgres — no proprietary storage — and a full export of your tenant’s data is available on request. We intend to be kept by preference, not by lock-in.
Will it work with what we’ve already built?
Yes — that is what the standards are for. Any OIDC-compliant client library connects without custom code. Your side of the integration is ordinary, boring, supportable — which is exactly how identity should feel.
The answers are short because the product was designed backwards from them. The prices are shorter still — the whole rate card fits on one page.
Foundation — by invitation. A free tier for organizations we invite.
Configuration
Describe it. Approve it.
In the console, tell the co-pilot what you want configured — an application, a role, a login policy — and it proposes the exact change. Nothing applies itself; you approve every line.
“Add an application for our staff portal.”
+ application staff-portal · redirect_uri https://portal.example.lk/callback
Awaiting your approval
Example proposal.
To proceed.
Point any standard OIDC client at login.developeroffice.com — the endpoints are exactly where the specification says they are. If you would rather begin with a conversation, write to us in Colombo and we will set your organization up properly.