Skip to content

Changelog

What’s new.

What changed in Synq, by day. Synq launched on 21 October 2026, and the entries before then are what it was built with. Follow it by RSS.

Every change to the management API, the account API and the MCP server is in the API changelog, and every SDK release in the SDK changelog.

  1. The SDK at 0.8.0 and 0.8.1, paying before a trial ends, clearer errors, and notes for upgrading

    • A trial with a saved card can end early: End the trial and pay now, on Billing, says what’s charged today, when the next charge is and where the receipt is. The management API and MCP can do it too, and an AI agent always asks you first.
    • Billing shows one state once a card is saved, every plan change sends an email naming the plan, the price and the day, and Keep and Renew undo a waiting move or a cancellation. Stripe’s “Canceled” is explained: only the paid plan ends, and the org, its brands and its users stay.
    • A request body that isn’t valid JSON gets 400 invalid_json, saying where it broke, and one sent without Content-Type: application/json gets 415 unsupported_media_type, not a 500. A missing field says it’s required and which values it takes, and a key’s refusal names the roles that would let it.
    • Every @synqauth package ships its CHANGELOG.md, and the docs’ new Upgrading the SDK guide says what behaves differently from one version to the next and how to keep the old behavior. The @synqauth/js guide shows Vite over https on your laptop, and the dashboard refuses an http:// redirect on a web app as soon as it’s added.
    • Rejoining an organization no longer brings back sign-ins from before you left. A new organization’s handle comes from its name, the dashboard says what an API key can do to other keys, when a former member’s access ended and who can invite you back, and the audit log names which of the organization’s fields changed.
    • A sending domain with all its records in place says so and verifies within minutes, and a brand’s sign-in host opened at its root leads to the brand’s account page. Moving a brand says up front that it needs a recent sign-in, keeps a refusal in its dialog and says how many members and invitations lose their role in the brand, and token gates say what happens to people who sign in without a wallet.
    • The dashboard puts the cursor in onboarding’s first field, keeps a fixed field’s old error away while it saves, ends long settings with a Save too and says when Copy worked. The sidebar counts invited teammates and updates the moment you approve, and the arrows that order the ways to sign in are bigger and easier to see.
    • An AI agent’s sign-in page changes say what they turn on or off, the sign-in preview says it tried your brand’s sign-in page, not your app itself, and get_reference’s schemas are flatter and shorter. The permissions reference says what each permission allows, and that no role needs org.read to open an org.
    • If Synq ever shuts down, the terms promise every org’s owners at least 90 days’ notice by email, and the export keeps working until then. About says what Aerosol stands behind, your users’ account page lists the apps they’re signed in to, each with Sign out, and deleting an account says what stays and for how long.
    • When your bank wants to confirm a payment that ends a trial (3-D Secure), Billing opens Stripe’s page for it and nothing is charged until you do, and Security says where Synq runs and how it recovers. Communities’ pages open for a teammate whose role is in one brand, a dashboard page survives one lost read, a secret shown once takes the keyboard focus, sign-in pages say why a link stopped working, and with Next 16’s Cache Components @synqauth/nextjs reads the session at request time, inside <Suspense>.
    • The Telegram bot’s “Connected” reply names your brand, gate pages show amounts with separators, and announcing a token gate’s window keeps going after you leave the page. npx synqauth init lists the changes it will make and asks once before making them (--yes skips it), a brand move asks the target org’s owners by email, and apps made with the API, an MCP host or init say source “api”.
    • The @synqauth packages are on npm at 0.8.0 and 0.8.1. See what changed and how to upgrade.
  2. The SDK at 0.6.0 and 0.7.0, plan limits up front, and a sign-in for any framework

    • When your plan has no room for another app, New app says so before you fill it in, names the app that holds the place and how to free it, and still lets a development app through.
    • Choosing “Something else” or “I’m not sure” during onboarding makes a single-page development app, and Get started shows the steps for any framework: @synqauth/js with its guide, or the values for any OpenID Connect library.
    • The docs show a whole sign-in with @synqauth/js, in a browser, in React and on a server, and @synqauth/react says up front that it needs a @synqauth/nextjs server.
    • Changing plan during a trial keeps the trial and charges nothing until it ends, and moving down to Starter happens on Billing.
    • An org’s default brand can be deleted once another brand becomes its default, and a webhook delivery says when it’s tried next.
    • Every page on a brand’s sign-in host, error pages included, refuses to be shown inside another site’s frame.
    • Synq’s Security, Contact and Support pages say how incidents are announced and that support aims to answer within one business day. Starter past 1,000 monthly active users stays free and working while Synq’s team gets in touch about Pro.
    • The @synqauth packages are on npm at 0.6.0 and 0.7.0. See what changed and how to upgrade.
  3. Free development apps, key rotation with an overlap, and sign-out that ends the brand’s session

    • From @synqauth 0.6.0, signing out of an app built on @synqauth/nextjs, or on @synqauth/js with its secret, signs the person out of the brand too, so the next Sign in asks how to sign in. With brandSignOut set to “ask”, the brand’s page asks first, as before.
    • An org’s development app, one whose redirect URIs are all on localhost, no longer counts toward its plan: Starter is one app plus a development app.
    • API keys rotate with an overlap: the new key is shown once, and the old one keeps working for the time you pick, up to 7 days.
    • Every plan can download its audit log as CSV or JSON, as far back as the plan keeps it, and Delete organization offers the download first.
    • Removing a teammate, or their leaving, ends their access to the org at once, and owners and admins can end a teammate’s sessions from Members.
    • Choosing Pro or Scale on the pricing page starts the new org on that plan’s 14-day trial with no card. Starter is free: past its 1,000 monthly active users, everyone still signs in and nothing is charged.
    • Webhooks say up front that they need Pro, and a finished delivery can be sent again from the dashboard.
    • An AI agent can give you a one-time link to try your brand’s sign-in before your site is up, and an app’s page has a Try sign-in button.
    • Refusals say more: a permission you can’t give says why, a 404 names what it didn’t find, and a field the API doesn’t take suggests the one you likely meant.
    • The docs have a guide to moving your users to Synq from another provider, and a Support page with where to write and what to send.
  4. A sign-in that leads with the emailed code, and plainer refusals

    • A brand’s sign-in page leads with the emailed code after the address, unless the brand chooses the password, and with the way the device last signed in, so someone who never set a password isn’t asked for one first.
    • The consent page says which account you’re allowing an app on, with “Use another account” to switch before you allow it.
    • Signing out of the Synq dashboard signs you out of Synq at once, so the next sign-in asks again.
    • When an AI agent asks for something your plan doesn’t include, such as a webhook on Starter, Synq refuses it straight away and says how to get it.
    • Deleting an organization cancels its paid plan’s subscription at once, and nothing more is charged.
    • The docs explain what an export gives you if you leave Synq, and the webhooks guide shows how to receive and verify webhooks on your laptop.
    • The website links the docs, the API reference, a live demo and Synq’s status page, and lists what Synq doesn’t do.
  5. A redesigned dashboard, Ways to sign in, and approvals for AI agents

    • The dashboard is redesigned: each page of a brand is cards with one Save, every list is a plain list, anything that can’t be undone asks first in a dialog, and on touch screens every control is at least 44px to tap.
    • A brand’s Sign-in page has a Ways to sign in editor: choose what’s shown first, what waits under “More ways to sign in” and what’s off. Its preview is the real page, which you can try.
    • An AI agent’s ordinary changes to your org apply as soon as it asks. Changes to money, people and sign-in security wait for your approval, and you or your org can choose to approve every change.
    • An approval request names the AI host that asked, says what it changes in plain words, and can bundle many changes that you approve once: all are made in order, or none.
    • ChatGPT connects to Synq’s MCP server, and MCP hosts such as Claude stay connected for up to 30 days after one sign-in.
    • Your Synq account lists the AI agents connected to it, with what each may do, and disconnects any of them.
    • Sending domains belong to a brand: each brand adds and verifies its own on its Email page.
    • Every code a sign-in can come back to your app with has a page in the docs, at /errors/<code>, with what it means and what to do.
  6. Brand moves, your own sign-in providers, and Enterprise security

    • An org’s owner can move one of its brands to another org. The other org’s owner sees what moves and what changes, and accepts it; the brand’s users stay signed in and its apps keep working. The new owner can then have Synq email the brand’s users once to say who runs it now.
    • On Scale and Enterprise, a brand can add its own OpenID Connect or OAuth 2.0 sign-in providers, from the dashboard, the management API and MCP.
    • Enterprise orgs verify their email domains on the dashboard’s Security page, the first step to signing their team in through their own identity provider, and can export their whole audit log as NDJSON or CSV.
    • Sign-in buttons show each provider’s official mark, and the wallet button shows your wallet’s own icon when it finds it.
    • People who sign in with a wallet that has an on-chain name, such as a Seeker ID, are offered it as their username. A brand can turn this off.
    • Members who verify from Synq’s Telegram bot sign in with one tap inside Telegram.
    • Every email Synq sends is light by default, with a real dark version for mail apps in dark mode.
  7. Brand roles, a dashboard to find your way in, and AI agents for everything

    • On Scale and Enterprise, give each member, API key and webhook endpoint a role in the brands they work on. Another brand reads as not there to them, and each brand’s Access page shows who can reach it.
    • Token gates belong to a brand, and apply only to its own apps, Discord servers and Telegram groups.
    • The dashboard has a sidebar with organization and brand switchers and ⌘K to jump anywhere, and opens on an overview of your brands, or of your brand: its numbers this week and month and what’s left to set up.
    • GET /v1/orgs/{org}/brands/{brand}/stats answers a brand’s users, monthly active users, sign-ins and new users.
    • The limit on how many organizations one person may own counts free organizations only.
    • An AI agent connected to Synq’s MCP server can do what an admin does in the dashboard: apps, users, members, billing, brands and communities. Whatever needs it waits for the person’s approval.
    • The @synqauth packages are on npm at 0.4.0. See what changed and how to upgrade.
  8. Token gates for Discord roles and Telegram groups

    • Connect your Discord servers and Telegram groups under Communities. Token gates give and take Discord roles and let people into Telegram groups, and check everyone again every 6 hours.
    • Members verify on your brand’s own member profile, where they add wallets, link accounts and see every gate live.
    • People already holding a gated role, or already in a gated group, get an announced window to verify, with a countdown, reminders and quiet hours.
    • Token gates can ask for recent on-chain activity: a number of transactions with a program or an address in the last days.
    • A brand can word every message Synq’s bots send about its communities. On Scale and Enterprise, an org can serve its servers and groups with its own bot, under its own name and picture.
    • Sign-in pages without a Solana wallet, such as Discord’s and Telegram’s in-app browsers, offer a link and a QR code to sign with your wallet elsewhere, and carry on once you do.
    • The docs have guides for giving Discord roles and guarding Telegram groups with token gates.
  9. Errors that say whose side a problem is on, and text you can read

    • Synq’s sign-in pages say whose side a problem is on and how to get past it, and tell you, the tenant, when your setup or plan is what stopped someone.
    • The dashboard shows every problem the API finds at the field it’s about, in words that say how to fix it, including plan limits and what your role can’t change.
    • Synq’s sign-in pages, emails, dashboard, docs and React components show no text under 13px, read body text at 16px, and keep small text at 4.5:1 contrast.
    • Wallet sign-in from an app’s own page asks for its request before the tap, so Safari no longer blocks the wallet’s prompt.
    • The @synqauth packages are on npm at 0.3.0. See what changed and how to upgrade.
  10. The account panel, avatars, and wallets on your own page

    • Add <AccountPanel> to your React app: an account button and panel for signing in, a first sign-in’s welcome and the person’s profile.
    • People can upload a picture or use a linked account’s, and every app can show a default avatar for anyone who hasn’t chosen one.
    • Apps can sign people in with a Solana wallet on their own page with no redirect, and add the connected wallet to the signed-in profile with one signature.
    • Tenants can ask a sign-in provider for extra scopes, per org and per brand, from a reviewed list, starting with Telegram’s phone number.
  11. npx synqauth init, an MCP server that asks first, and safer account linking

    • Set up a Next.js App Router app with Synq sign-in with npx synqauth init, or npm create synq.
    • The docs have a “Use with an AI agent” guide: connect Synq’s MCP server to Claude, Claude Code or Cursor, and approve what your agent asks to change.
    • A brand can let people move a way to sign in from one of their accounts to another, once it opts in, and people are asked to link an existing account before making a second one.
    • Making an API key, rotating an app’s or a webhook’s secret, and setting a sign-in provider’s app ask you to sign in again when your sign-in is more than 5 minutes old.
    • Resend a webhook delivery that your receiver missed.
    • The docs have a dated API and MCP changelog.
  12. Trials on Pro and Scale

    • Pro and Scale start with a 14-day trial and no card. The billing page shows your trial and previews a plan change, and members can ask the owners to upgrade.
    • New organizations are offered their website’s logo and a sign-in color, which you confirm.
    • Report brand impersonation, phishing and abuse from Synq’s contact page.
  13. Sign in with GitHub, and the ways in each app takes

    • Tenants can offer sign-in with GitHub, through Synq’s GitHub app or their own, and read each GitHub account’s type, age, public repositories and followers. Developers can sign up for Synq with GitHub too.
    • Turn a brand’s built-in ways to sign in off, and let an app take only some of its brand’s ways, GitHub and Google alone, say.
    • Apps can ask for the linked_accounts scope, and APIs for identity_claims, to learn which accounts a person signs in with.
    • On Synq’s preview, an app’s end-to-end tests can sign in as a made-up GitHub or Google account of the age and kind they name.
  14. Synq launches: anyone can sign up

    • Anyone can sign up for Synq with a verified email, make an org and start on the free Starter plan. Paid plans are bought in the dashboard.
    • Setting up takes one field and shows your own sign-in working within a minute, on a phone or a laptop. Try your brand’s sign-in page as one of your users before writing any code.
    • Sign up with Google, Microsoft, Telegram, Matrica, an emailed code or a passkey.
    • Synq has a public status page.
    • The @synqauth packages are on npm at 0.2.0. See what changed and how to upgrade.
  15. Sign-in on your own screens, and API keys for your users

    • Apps can sign people in on their own screens, with a password or an emailed code, through the issuer’s /authorize-challenge endpoint (OAuth 2.0 for First-Party Applications). Turn it on per app; <SignInForm> and useSignIn() do it in React.
    • Your users can make API keys for your API from your app, and your API checks them with Synq. Turn them on for an API in the dashboard.
    • An app can insist on a passkey sign-in with an essential acr claim.
    • People on Android can sign in with their Solana wallet app from the hosted sign-in page in Chrome.
    • People who sign in with X, Discord, Telegram or Matrica see their @handle under their ways to sign in.
  16. Claude connects to Synq’s MCP server

    • Claude and Claude Code can sign in to Synq’s MCP server.
  17. Passkeys before sensitive actions, and safer account linking

    • Apps can ask for a passkey before a sensitive action, with acr_values=urn:synq:loa:2.
    • A Microsoft sign-in links to an existing account only when Microsoft confirms who owns the address’s domain, and a Google Workspace one only for addresses on the Workspace’s own domain.
    • People who sign in only with Apple, Facebook, X, Discord or Telegram can add another way to sign in, such as a wallet or a passkey.
    • Synq checks the signature of every ID token a sign-in provider sends.
  18. Sign-in errors that say what to do

    • Sign-in refusals say what to do: which way an existing account signs in, and how long a hold lasts.
    • Error pages say what went wrong in plain words and link back to the app, and refusal pages offer “Use another account”.
    • Too many sign-in tries say so on the sign-in form, with the other ways to sign in still there.
    • A password reset link that no longer works lets people ask for a new one right there.
  19. Sign-in on your own domain

    • On Pro and up, a brand’s sign-in can run on a domain you own, such as login.acme.com. Add one CNAME record, and Synq checks it, issues the certificate and emails you when it’s live: a second issuer for the brand, with the same users, apps and keys.
    • The dashboard’s Domain tab walks you through it, with the record to add, each problem’s fix, and what to change in your apps. The management API and MCP can add and check one too.
    • Passkeys made on your brand’s Synq host also work on your domain, in browsers that support related origins.
    • If your plan changes to one without custom domains, the domain keeps working for 14 days, and an upgrade in time keeps it.
  20. Email from your own domain, and replies that reach you

    • On Pro and up, your brands’ sign-in email can come from your own domain, such as mail.acme.com, signed with it. Add the domain, publish its DNS records, and Synq verifies it and keeps checking it; whenever it can’t send from your domain, the email still arrives, from “Acme via Synq”.
    • On every plan, set where replies to your brand’s email go. The address is used once someone who reads it confirms it, and without one, replies never reach Synq: the email says they aren’t read.
    • The dashboard has an Email domains tab for each org and an Email tab for each brand, with exactly what your users’ next email will carry and a test you can send yourself.
  21. Your own provider apps on your own host, and every provider in MCP

    • An app you bring to a sign-in provider now sends people back to your brand’s own sign-in host. Register your brand’s own callback with it; an org-wide app registers one callback per brand.
    • Apps built on @synqauth/nextjs can add a way to sign in to someone’s account, and signing in again in the same browser no longer signs the person out.
    • MCP hosts can turn Apple, X and Facebook sign-in on and off, and the tools name every provider.
  22. Social sign-in, passkeys, token gates and plans

    • Brands can turn on sign-in with Google, Microsoft, Discord, Apple, X and Facebook, through Synq’s apps or your own.
    • People can sign up and sign in with passkeys that the issuer verifies itself, and your apps can ask them to add one.
    • Sign in with any Solana wallet that follows the Wallet Standard, against a request the issuer makes for each sign-in.
    • Orgs on Pro and up can gate sign-in on token holdings, checked at every sign-in and refresh. When a gate refuses someone, they can add the wallet that holds the tokens right there.
    • People can add a wallet, Google, Microsoft or an email address to their account, and remove one, from your app.
    • The sign-in page shows “Last used” on the way someone last signed in on that device.
    • Every org has a plan, listed at GET /v1/plans, and GET /v1/orgs/{org}/billing/usage shows its monthly active users against its allowance.
    • Ending a user’s sessions, disabling them or resetting their password tells your apps through back-channel logout.
    • People and tenants can see and withdraw the consents Synq remembers.
    • Synq’s MCP server lets your admins read your org and make small changes from an MCP host.
    • Next.js and React apps can sign people in with @synqauth/nextjs and @synqauth/react, with every Synq token kept on the app’s server.
    • A flood of events at one org no longer delays other orgs’ webhooks.