Linker

Protect user identity in Kazakhstan.
Keep your global stack.

Secure authentication and Kazakhstan-resident identity data, through one SDK.
We handle credentials, sessions, and local infrastructure. You keep building your product.

Add Linker auth to my app: https://linker.kz/SKILL.md

Agent guide preview · early access

01 — The work behind the login

A server is cheap.
Owning authentication keeps costing you.

You can build the first login flow with AI. Then you own another critical production service: hosting in Kazakhstan, recovery flows, security updates, backups, and incidents. Every change needs care, long after the first deployment. Linker takes on that ongoing work.

  • Account protection
  • Password recovery
  • Session security
  • Local servers
  • Backups
  • Monitoring
  • Ongoing maintenance

02 — What Linker takes care of

Your team ships the product.
Linker handles authentication.

Your app uses the SDK. Linker maintains the authentication flows and Kazakhstan infrastructure behind it, so your team doesn’t need to become authentication specialists.

If you know Clerk, the ambition is a similarly straightforward developer experience, built around Kazakhstan-resident identity. Planned local authentication methods include multi-OTP through SMS, WhatsApp, and Telegram at the same time, plus EDS/mGov authentication. If these methods are your main reason for joining early access, let me know in the signup form so we can discuss what your app needs.

One session check. All the steps behind it.

Your app asks for a valid session. Linker handles what “valid” requires today.

In your app

const session =
  await linker.requireSession()

A user opens your dashboard.
Your route asks for a session.

Back at your dashboard

session.userId
// "user_831…"

The page resumes with a ready session.
Your product logic takes it from here.

Handled by Linker

  1. Your app calls requireSession()

    Linker checks whether the session is ready.

  2. Access token expired

    SDK attempts refresh.

  3. Required profile fields changed

    This project now requires phone_number.

  4. Hosted completion flow

    The user adds and verifies their phone.

  5. Fresh session issued

    Linker returns the user to the original route.

Linker handles and maintains the edge cases of authentication, so you can rely on them working correctly as your product evolves.

Keep building with the tools you know.

Keep your frontend and backend where they work for you. Linker manages identity and credentials in Kazakhstan; your app keeps user references, product data, and access rules. We help map which data belongs where for your integration.

Give account security a dedicated owner.

Sign-in is only part of the job. Linker handles verification, recovery, credential protection, and sessions together—so your team has less security-sensitive code to build and maintain.

Get local infrastructure off your to-do list.

A hosting bill is only part of the cost. Linker takes on auth servers in Kazakhstan, backups, monitoring, and ongoing maintenance, so another critical service doesn’t become your team’s permanent job.

Keep identity data in-country.

Linker-controlled identity data and processing stay in Kazakhstan, including backups and operational systems. Keep the rest of your stack where it works for you.

03 — Before you switch

Less work shouldn’t mean more unknowns.

Know what switching involves, what Linker takes care of, and what stays in your hands.

Will my existing users need to sign up again?
Bring your existing accounts with you through supported migration. We check compatibility with your current user and credential storage before cutover, so you know what moving involves before you switch.
How much of my app will I need to change?
At release, we aim to support a Next.js integration, a React client SDK, and HTTP integration for backends, with hosted sign-in and recovery. Backend language and migration compatibility will be checked for your application. Your product data and access rules stay in your app. You replace your authentication integration, not your entire stack.
Will I have to deal with infrastructure issues?
Your users need a reliable way in, not a window into our infrastructure. Linker is built to keep authentication steady while we handle monitoring, maintenance, and recovery behind the scenes. Keeping the service running is our job.
Who takes care of my users’ data?
Linker manages your users’ data end to end—from secure storage and processing to backups and ongoing protection, all in Kazakhstan. You get authentication and the data infrastructure behind it as one managed service, without making their upkeep another job for your team.
What if I outgrow Linker?
Your user data is exportable, and the exit path is documented. If you need another provider or a different authentication flow, you can move on. Migration compatibility depends on the destination you choose.
Will I have to keep chasing SDK updates?
Every version of Linker is built to be complete and supported for the long term. Long support horizons give your team plenty of time to prepare for upgrades and fit them into your roadmap. Clear support timelines and upgrade guides help you move when you’re ready.

Start small.
Plan for growth.

Target launch pricing for the base package. Start with a free allowance, then pay for the monthly active users above it.

Base package · target pricing

First 1,000 monthly active users
Free
Each additional monthly active user
₸15 / month

One allowance per customer across all projects. A monthly active user (MAU) is a distinct user who successfully authenticates during a calendar month.

This is our target, not a final price commitment. Pricing may change as Linker’s capabilities grow. Final billing terms will be confirmed before launch.

Linker is in development. Joining early access does not start billing.

04 — Who’s building it

Built by an engineer who has operated critical systems in Kazakhstan.

Previously worked at

gexabyte.IT AnalyticsMyRadius

I’m Ivan, a backend engineer based in Kazakhstan. My work has included fiscal-data infrastructure, government integrations, and production systems where losing data has real consequences.

I’m building Linker so teams can serve Kazakhstan users without taking on all that authentication and infrastructure work themselves.

I’ll personally help every team onboard and work through its existing-account migration. If you later decide to leave Linker, I’ll help you migrate out too. I want both experiences to be as straightforward as possible.

Talk to me about Linker on Telegram · @ivanlukov

Ivan Lukov · Backend / distributed systems engineer

05 — Early access

Bring your stack. Let’s map your move to Linker.

Already building your own auth or have users to migrate? Tell me your stack and what handles authentication today. I’ll personally help map what stays in your app, what moves to Linker, and which migration gaps we need to resolve ahead of the planned November 2026 early release.

By submitting, you’re asking Linker to contact you about early access. Read how your details are handled in the Privacy policy.