Novidades do Subscriby

Subscriby 5.3.0

Changed

• The retired brand's domain bridge is gone. Its redirects and the webhook passthrough, the migration commands and notice-only mode of the retired platform bot, and the old announcement article that named it are removed; every address on the retired domain stops answering, and the guard that keeps the old name out of the codebase now allows no file but itself.
• Pages, the portal and the API answer from an application kept in memory between requests instead of one started afresh for each, so every page and call is quicker to begin. Nothing of one request reaches the next: the test suite now drives request after request through the same server process and proves it, and every server process reports its memory so a change that leaked would show as a rising line, not as a slow site.
• An account that has not chosen a plan yet gets five one-time Subscriby Copilot turns to try it, and no more: they never renew, and once they are used the Copilot asks for a plan. The monthly free turns belong to the plans, so they begin the moment a plan is active, the Free Plan included; an account that had not chosen a plan used to be shown a full month of free turns it had not got.

For developers

• The connector SDK is 1.17.0. 1.17.0 adds Core\Storefront::startHostedCheckout() for a connector that runs its own checkout screen, Core\PassRoster and the pass_roster command for the Pass Roster on a creator surface, and lets a package declare a list of listeners for one SDK event. 1.15.0 added BroadcastReach::$broadcastId, the record a queued send reports into, so a creator surface that queued a broadcast can name it in its follow-up; 1.16.0 adds the kind-label reads on Resources (memberKindLabel, creatorKindLabel, memberKindBadge), the words the core uses for a kind of place named after its connector, the listing's brand_color, which the member portal paints the connector's buttons in, and Grants::listWaitingForSubscription() with MembershipSummary::$waiting, the places a purchase waits for because the member holds no account on their connector. The SDK docs carry a page per contract.

Fixes

• A Discord server's Pass windows as server events choice, the default or one place's own, applies the moment it is saved instead of at the next morning's sweep, and a pass window already open when the choice is saved, or first seen while open, gets a live event, scheduled a minute ahead and started at once.
• The home page's Message Broadcasting card names every platform its pacing covers instead of the first one alone, and its progress bar sits with the heading instead of leaving a gap above it.
• Every marketing sentence about a community on whichever platform it lives now says "Telegram or Discord" where it said "Telegram" alone: the comparison, vertical, gateway and legal pages, in every language. A sentence that means one platform, a competitor that serves Telegram only or a Stars payment inside Telegram, still names it.
• The pricing cards' three badge pills, Addon, the check cadence and the Copilot allowance, share one padding and one gap again; two of them had been squeezed tighter than the third. On a phone the cards keep their rows whole by sitting their content a little closer to the edge instead.
• A coupon on a one-time plan sold through a connected Stripe account opens its checkout again, on the web and in the bot alike; the step that corrects the platform's fee for the discounted total had stopped the checkout before it opened.

Subscriby 5.2.0

Features

• Two new ways for your members to pay. Polar is a merchant of record: it collects the payment, handles sales tax and VAT in every country it sells into, pays you out in 120+ countries through its own Stripe rail and renews monthly and yearly plans on its side; you paste one organization access token, your plans are pushed to Polar as products, and the webhook is registered for you the first time a plan syncs. Mollie brings Europe's rails: iDEAL, SEPA Direct Debit, Bancontact, cards and PayPal in 29 currencies, with renewals on the mandate a member's first payment leaves behind; you paste one API key, whose prefix tells test from live, and nothing else is needed. Coupon codes work on both, on one-time and recurring plans alike: a recurring plan is discounted on its first charge and renews at full price.
• Polar and Mollie have their pages under Payment Methods on the site, and every comparison, switch guide, vertical page and connector listing that names the gateways names them too; the home page's processor strip shows both marks.
• A third merchant of record, Kelviq: it collects the payment, calculates and remits sales tax and VAT wherever it sells, pays you out in 90+ countries through its own Stripe rail, and renews monthly, quarterly, half-yearly and yearly plans on its side, emailing the member a payment link when a card fails and retrying up to eight times over fourteen days while Subscriby keeps its own grace window with the same link. You paste one Server API Key; your plans are pushed to Kelviq as plans with their prices the first time they sync, the webhook endpoint is registered for you, and a sandbox key makes a Test method that pays with a test card through a real checkout. Coupon codes work on one-time and recurring plans alike: a recurring plan is discounted on its first charge and renews at full price.
• Kelviq has its page under Payment Methods on the site, after Mollie wherever the gateways are listed: the pickers, the comparisons, the switch guides, the vertical pages, the connector listings and the home page's processor strip. The strip now shows twelve marks, six to a row, and Telegram Stars is among them before Access Codes, drawn with its own mark and opening the in-app payments page. Hovering a mark on the strip opens a card like the connector chips have: the method in one line, the three reasons creators pick it, where it works, what buyers pay with and how many currencies it settles in. The card opens above the mark when the screen below it is short and stays inside the window at the row's ends.
• Discord is open to every creator as a public beta: the invitation the private beta needed is gone, and its card carries the Experimental badge while it matures.
• Every broadcast is kept: who sent it and from where (the dashboard, your bot, the API or the Copilot), its audience and message, and as it sends, how many got it, how many did not and why, down to the member and the reason the platform gave.
• When a broadcast finishes you hear it once, in the bell and in your bot chat: how many got it, how many could not be reached and how long it took. A send the worker had to refuse says why. Broadcasts is a new alert class under Alert Destinations, so you choose where that notice goes.
• Confirm a broadcast in the Copilot and watch it go: the step under the reply counts the sends as they happen and ends with how many got it, how many did not and how long it took, with nothing more charged. On your bot, the answer closes with the same line.
• A Broadcasts page on every project, in the sidebar after Users: every message that went out, who sent it and from where, which audience, how many got it, who could not be reached and why, with a flyout for the message itself and the members it missed, live while one is still sending. History starts with this release.
• Retry the members a broadcast could not reach, from the Broadcasts page, the API or the Copilot: a new broadcast goes to them alone, under the old one. A past broadcast opens in the composer again with Resend.
• Every action the Copilot takes on your confirmation ends with what happened under its step: Archived, Deleted, Cancelled with the holders affected, Sent to 31 of 33. On your bot, the answer closes with the same lines.
• Every piece of work the Copilot queues on your confirmation reports back under its step as it runs: a batch of access codes, an account export and a reverted channel recovery say when they finished and what they counted, live, with nothing more charged.
• Create Members Area builds a fuller server: three private categories, Info with #start-here, #announcements and #resources, Community with #general, #introductions and #help, and Voice with a Lounge and an Events room, each text channel carrying its purpose as its topic, beside whatever the server already has. Nothing is replaced, and a category or channel the server already had under one of those names is named in the answer.
• Discord's App Directory leads straight into Subscriby: its Add button opens the Discord page with the Connect dialog already open, a creator with no project names their first one right there, and Connect sends them to Discord's authorisation page at once; back from Discord the server is connected. A social sign-up now returns to the page it came for, and /subscriby-admin connect in a server nobody connected offers the same door.
• Your Telegram bot lists ten plans on a page instead of five, so a catalogue the size of most projects is on the first screen; the Storefront Order you arrange on the dashboard is the order the bot shows them in.
• Every place a plan includes is named after its platform, with the platform's mark: Telegram Channel, Discord Role, and for a Discord place the server it is in. The portal's plan cards, the plan editor and the bot's plan, pass and join screens all say it the same way; a perk you added by hand stays a Custom Perk.
• A purchase that includes a place on a platform you have not connected yet says so wherever you look. The receipt, your membership page, your bot's access screen and /subscriby status list every place with where you stand on it: You are in, Tap to join, Opens with the window, Handed over by the organiser, or Waiting for your Discord account with a Connect button in the platform's colour that opens the portal signed in with the connect flow already started. The moment the account is connected the place is granted and you are told in your chat and by mail.
• Pick a plan that includes a place on a platform you have not connected and the checkout offers to connect it before you pay, with the platform's own link and the words to type there, so the access arrives with the receipt; Later puts it off. Your bot offers the same two routes for a place still waiting: the other platform's door and its command with your code, so you never need the portal in between.
• A member whose place is still waiting on an account they have not connected is reminded once, a day after the purchase and a day before a pass window opens, in their chat or by mail, with the door that connects it. The switch is under Revenue Recovery → Settings, on by default; a member who stopped your follow-ups is never reminded.
• The Members page gains a Waiting on a Connection tab for the members whose purchase includes a place on a platform they have not connected, a chip naming that platform on their row, and in their flyout the places themselves with Remind to connect, which sends the reminder with the door at once, once a day.
• Broadcasts gain a Waiting on a Connection audience, the members whose purchase includes a place on a platform they have not connected, from the composer, the bots, the API and the Copilot, on every plan.
• The member portal shows Open Discord Server beside Open Telegram Bot when a project runs both: the button opens the server at its own address, which Discord shows only to the people already in it, never an invite; the membership screen's and the portal Copilot's buttons take the same connector's words.
• A rolled-over pass shows its move under the purchase in the member flyout, from which date to which and when, and a date that holders were moved onto says N moved here on the Pass Windows page, so a season of cancellations can be followed without opening each plan.
• Every move of a pass is kept: from which date to which, why and when, and the member flyout shows the whole trail of a pass moved more than once, where it used to show only the last move. A purchase whose payment settled after its window is recorded as a move too, from the date it missed to the date it was given.
• A Pass Roster page on every project that sells dates: a timeline of every member against the coming dates, every date drawn to its real length, where each member stands on each date (in, queued, holds, missed, ended, covered), cancelled dates dashed with an arrow to where their holders were moved and how many, a hover line with the exact time, a dialog behind every date (its roll call, holders and moves), every pass (its source, queue, access, reminder, payment and trail) and every member (status, dates held, the whole trail), a Past tab, a plan filter, a search, and a CSV of the grid.
• The home page's features band opens with a card on who the product answers to: a bootstrapped company with no board of directors, no investors and no pitch deck to dress features for, three refusals each paired with the promise it buys, and a panel of creators' feature requests going from asked to building to shipped, with the count of board meetings held at zero.
• The home page's features band closes with the Pass Roster as a creator sees it: four members' weeks scrolling past on their own, dates opening, queues, a cancelled night rolled forward and a date cancelled twice, built ahead and cleared behind as the weeks go by.
• The About page tells the founder's story in his own words, with his photo and signature: a paid community run from Sri Lanka on bank transfers and screenshots, the rented bot that took a cut of every sale, the pricing that priced him out, and the tool he built instead, with the journey in six steps and four principles beneath it. Instagram joins the brand's profiles in the footer and on the page.
• Public holidays on the Pass Roster: the holidays of the country on your profile are tinted a pale pink down the whole timeline, with the holiday's name written up the column, level with the rows on your screen, so a date is never scheduled onto a holiday unknowingly; every country's holidays are refreshed once a month from Google's public holiday calendars, and a team member sees the project owner's country.

Changed

• The portal's Account & Recovery page is redesigned around what a member does there: an identity strip with your initials, when you joined and where the project's notices go; every connected account in one shape, the platform's mark, the name and handle, a line saying whether notices reach you there, Open at the right, and the account's settings on a line of their own with Disconnect at its end; a Notices card for the email copy and the follow-up messages; and the destructive actions as quiet red links instead of pills.
• The home page's Markdown mirror and llms.txt carry the whole features band: the independence card, every feature card and the Pass Roster card, so an agent reading the site as text learns what a visitor sees.
• The dashboard preview on the home and sign-in pages runs on every connector you can install today, Discord beside Telegram in its By Connector card, its plan and transaction rows and its sidebar; and a phone now sees that preview as one tall picture of the dashboard without the sidebar, scrolling with the page, where a small frame used to scroll it past at speed.
• The alert for a place a connector can no longer manage names the connector in its title and its first line, on the bell, by email and on the bot, so a creator who runs two connectors knows which one to open.
• A connector action's choice fields, such as the per-place events setting, are Flux listboxes like every other select on the dashboard, no longer the browser's own menu.
• The resource editor offers one list of cards, one per kind, each named after its connector with its mark: Manual Perk, Discord Role, Discord Channel, Discord Server, Telegram Channel and so on, with a line on how each is added. Choosing a card switches the form below it at once, with no request and no spinner; the places a connector lists are read once when the editor opens. The page's tabs carry the same names, so two connectors' channels no longer share a tab label.
• The Discord row's actions read like the rest of its menu: Set Removal Rule, Create Members Area and Mirror Pass Windows.
• A row of tabs that outgrows the window no longer shows a scrollbar: it fades at the edge that still has tabs beyond it and scrolls under a mouse drag, as the rates strip does.
• A connector action's notice is headed by the action's name and says in a line what it did; Create Members Area no longer reads out every channel.
• A resource's kind reads as its connector names it wherever a page badges it, Discord Role or Telegram Channel rather than Role or Channel, and the plan editor's resource picker shows the connector's mark beside each resource.
• The portal's sign-in sheet draws each platform's own mark on its buttons and paints them in the platform's brand colour, Telegram's blue and Discord's blurple, with text that reads on it; the email and social options keep the portal's design.
• The Copilot panel slides in from the edge and fades out instead of appearing at once: its stylesheet only ever animated its width, so the entrance and exit declared on it never ran.
• The portal's sign-in sheet lists the sign-ins first, each platform's Continue button in its colour, then Google and the email link, and keeps Just open as one quiet row of small pills at the end instead of a Just open, an or and a Continue per platform; Telegram's colour is the app's deeper blue; the sidebar's platform buttons stand full width in one tight stack.
• The portal's platform-coloured buttons are a light tint of the platform's colour with a tinted edge and the words in the colour itself, deepening a little on hover, so the platform's mark and the words read on them and a row of them sits as calmly as the plain buttons beside them.
• Slack is next up: the Connectors Marketplace, the home page and every sentence on the site that names the connector in development now say Slack, and WhatsApp and the rest stay on the roadmap.
• The project menu runs Project Dashboard, Connectors, Resources, Payment Methods, Subscription Plans, Access Codes and Coupon Codes, then Subscriptions, Users, Support Inbox, Broadcasts and the Pass Roster, then Smart Links, Referral Program, Revenue Recovery, Portal Designer and Knowledge; the dashboard preview on the home page shows the same order.
• The home page's live dashboard preview opens with the Copilot sheet showing its conversation from its first question beside the dashboard; the × closes it and Ask Copilot in the sidebar brings it back.
• The home page's Pass Roster showcase draws the public holidays of the visitor's own country as its clock approaches them, tinted and named up the column exactly as the dashboard's roster draws them, from a public per-country holiday feed; the country is read at the edge from the visitor's address and nothing about the visitor reaches Subscriby.
• The portal's sidebar card scrolls with the page when it is taller than the screen and stays put only when its edge meets the screen's edge, on the way down and on the way up, so a long or expanded description is never cut off; a card that fits the screen stays in view as before.

For developers

• The connector SDK is 1.16.0. 1.15.0 added BroadcastReach::$broadcastId, the record a queued send reports into, so a creator surface that queued a broadcast can name it in its follow-up; 1.16.0 adds the kind-label reads on Resources (memberKindLabel, creatorKindLabel, memberKindBadge), the words the core uses for a kind of place named after its connector, the listing's brand_color, which the member portal paints the connector's buttons in, and Grants::listWaitingForSubscription() with MembershipSummary::$waiting, the places a purchase waits for because the member holds no account on their connector. The SDK docs carry a page per contract.
• POST /v1/projects/{project}/broadcasts, broadcast_message and a bot's broadcast answer carry broadcast_id, and broadcast.queued and broadcast.completed now carry it too, so a webhook consumer can tie the two events to one send.
• GET /v1/projects/{project}/broadcasts, /{broadcast} and /{broadcast}/failures list every broadcast with its status, its tallies, the sentence the creator reads and the members it could not reach with the reason for each, under the new broadcast:read ability (a token minted with * already holds it); list_broadcasts and get_broadcast are the same for an agent, and broadcast_message says where to follow the send.
• POST /v1/projects/{project}/broadcasts/{broadcast}/retry and retry_broadcast queue that retry; broadcast.queued and broadcast.completed carry parent_id, null for a first send.
• revert_recovery_operation answers job_id for a channel revert, which get_job_status follows like a code batch or an export; every mark a tracked job takes now reaches the Copilot step following it live.
• GET /connectors carries brand_color, the platform's brand colour from the manifest's listing.brand_color, null when the connector declares none.
• GET /v1/projects/{project}/members?access=waiting keeps the members whose live purchase includes a place waiting for an account they have not connected, and POST /v1/subscriptions/{subscription}/remind-connection sends that member the reminder with the door; the Copilot's list_subscribers takes access: waiting and remind_member_to_connect does the same.
• A payment method's provider may now be polar or mollie, on the REST API, in the Zapier and n8n apps and in the Copilot's provider list. Both rails emit the same events as the others, payment.succeeded, payment.failed, payment.refunded, subscription.activated, subscription.renewed, subscription.past_due and subscription.cancelled, and a member's billing_email is captured from both. Polar's webhook endpoint is registered on the creator's organization by the plan sync; Mollie's notifications are read back from Mollie before anything is recorded, so neither needs a webhook configured by hand.
• A payment method's provider may now be kelviq, on the REST API, in the Zapier and n8n apps and in the Copilot's provider list. The rail emits the same events as the others, and a Kelviq payment.failed carries no extra field: the member's payment link is Kelviq's own, sent by Kelviq and repeated by Subscriby's grace notices. Kelviq's webhook endpoint is registered on the creator's organization by the plan sync, and every order is read back from Kelviq before it is recorded.
• pass.holder_moved and pass_series.leg_substituted carry reason (window_cancelled, series_date_substituted, paid_after_window) and move_id, and pass.holder_moved now also fires for a purchase bound to the next date after a late payment. subscriby:passes:backfill-moves writes the moves the ledger remembers from before the log, once.

Fixes

• Signing in to a portal with Discord stays on the portal. Discord's authorisation page named the dashboard's address as where it would send you, the tab it returned to was a dashboard-styled page, and its Open the portal button landed on a portal that was not signed in yet, because the only thing signing the portal in was the tab you started from, polling at a twentieth of its rate while it was in the background. The member door now lives on the portal address end to end, the tab Discord returns to lands on the portal signed in, connecting an account from Account & Recovery lands back on that page with a word of success, a refusal lands on the portal with the reason, and the tab you started from signs in within two seconds whether or not it is in front. The bot's Return to Portal button after a Telegram sign-in signs you in the same way.
• A member's first connected account is their preferred one, as the API has always said. The bot's registration path never flagged it, so a member who connected a second platform saw Set as preferred on both rows and none marked while the notices quietly went to the oldest account; every such member is repaired at the deploy, and disconnecting the preferred account now hands the flag to the oldest remaining one.
• A creator with accounts on two platforms gets their bot notices again, where they belong. A sale, a pass roll call or a window opening went to one account only, whichever the database listed first, and a Discord account had no bot to go through, so a creator who linked Discord beside Telegram was told nothing on either. A notice about something that happened on one platform (a sale by a member there, a pass window on places there, a member a place holds out, an incident of its installation) now goes to your account on that platform when Alert Destinations route the class to it, and to your other accounts only if that one could not take it; a notice with no platform of its own goes to every account you route it to. Discord's are sent through the Subscriby app itself, and the bell's copy to a Discord account arrives too.
• A pass window whose creator nobody can be sent the opening notice, no connected account or none the bot can write to, is marked told and left alone instead of being retried every minute until it closed; a notice the platform refused is still retried, and the hour-before reminder behaves the same way.
• A request that sets a property a component does not have is answered as a bad request and counted against the sender, the way a forged upload call already was, instead of failing as a server error.
• Twenty page descriptions that grew past the search-snippet limit when the second platform joined the platforms line are shorter, with room for the next platform, and the audit that guards them now lists both platforms the way the live site does.
• The Connector column of the dashboard tables names every connector on a row beside its mark; a row on two connectors showed two bare icons under a neighbour that read "Telegram", as if its names had failed to render.
• The Connector Doctor no longer asks for the Subscriby role to be dragged above a Discord role that already sits below it. Discord gives a role made through the API the same position as the app's own role and ranks the two by age, so the doctor read every role the app had just created as above it; it now ranks roles as Discord does.
• Subscriby Copilot answers "what's wrong with my connection?" from the connector itself: it reads each connector's state, runs the doctor for a finding per place with its fix and reads the open Disaster Recovery incidents, instead of saying it cannot see a connector's health. Those three tools now travel up front on every turn, and the Copilot is told that every area of the dashboard has a tool, so it searches before it declines.
• The Connector Doctor dialog's verdict badge no longer sits under the dialog's close button.
• The Discord creator commands register again. Discord allows one slash command 8,000 characters of names and descriptions, and /subscriby-admin had grown past that, so Discord refused the whole set and the beta's server had no slash commands. The creator toolkit is now three commands: /subscriby-admin for the everyday business, /subscriby-growth for the Referral and Partner Programs, Smart Links, Revenue Recovery and the portal's design, and /subscriby-support for the inbox, the relay forum, your tasks and Disaster Recovery; /subscriby for members is unchanged, and a test holds every command inside Discord's limits.
• Deleting a resource now closes the Disaster Recovery incident that was open about it, and the hourly health walk closes any incident whose resource is already gone, so a place you removed no longer shows as detected or keeps a Fix button that leads nowhere.
• A tier is named with a capital P everywhere: Starter Plan, Growth Plan and Free Plan, on the connector cards, in the dashboard, the bots, the emails, the API's answers and the docs.
• The exchange-rate strip above the dashboard is back. The project tabs' new scrolling strip laid it out at its full width, hundreds of thousands of pixels, so only its heading was on screen and the header could be dragged; the strip now sits in a column of its own on the dashboard.
• Linking a place to a pass plan whose dates already exist tells the connector at once, so a Discord event for a newly linked role or channel appears without waiting for the nightly catch-up; unlinking a place withdraws its events.
• The series editor's pass tiles keep the time on one line and show the end date beneath it, instead of breaking the time in two when a tile is narrow.
• The project tabs open on a click again. Since the strip learned to scroll by dragging, it took hold of the pointer on every press, so the click that ended a press landed on the strip instead of the tab under it; the strip now takes the pointer only once a press has moved far enough to be a drag.
• The changelog reads the announcements' category once, with the announcements, instead of once per announcement, and so does the Markdown copy of a blog category.
• The nightly exchange-rate refresh writes every currency's rate in one statement and leaves one line in the activity trail listing each old and new rate, instead of an update, a re-read, a log row and a search sync per currency.
• Every comparison, switch guide, feature page, integration page and the changelog now tell search engines and AI crawlers that they are articles, with the day each went live and the day its facts were last checked, and the blog's listings say they are collections of the articles they show, so a site audit no longer reports them as articles without structure.
• Every link in the footer offers a full-size tap target on a phone, so the legal links are no longer reported as too small or too close together.
• On a phone, every feature card on the home page grows with its text instead of cutting it off at the bottom, the counter and payment tiles keep their figures on one line, and the pricing list's check-cadence badge stays with the last word of its label; on a desktop the band's three columns still end level, one card in each taking the slack.
• On the sign-in page in the light theme, the quote card has the same thin outline as in the dark theme and no drop shadow, and switching the theme shows the other theme's dashboard picture at once: it is fetched while the page is idle after loading instead of at the switch, which used to take a few seconds.
• Creating an account writes the new team's three roles with one statement per role instead of one per permission, about a hundred and fifty fewer queries behind every sign-up.
• The holiday refresh keeps a region list of any length: Switzerland's calendar names all twenty-six cantons that keep a day, the list overran the column, and the country's holidays were not written on the first refresh.
• A Discord slash command or button the bot answered from its queue failed from the worker's second job on with "Current user must be set before accessing projects": the Core API adapters the worker keeps between jobs held the first job's tenant context while the services read the current one. A context held across jobs now acts on the job that is running.
• Every status tab of the account-wide Members and Subscriptions pages showed its skeleton, reloaded once and then said the page could not load: the tab's filter was read as a project named "all" and the page answered 404. The tabs load again.
• On the pricing cards, the note behind a plan's check-cadence or Addon badge ran off as one long line across the next card, and on a phone it was cut off at the card's edge. It wraps inside its card now, and the feature lists sit evenly inside their cards, which also keeps "Disaster Recovery Program" and its badge on one line on a phone.
• In the home page's dashboard preview, the Copilot sheet kept the mouse wheel even when its conversation was already at its top or its end, so the page would not scroll while the pointer rested on it, and a turn moved the conversation a notch at a time. At either end the wheel scrolls the page again, in between it glides the conversation, and the sheet slides in and out when opened and closed from the sidebar instead of flashing.

Introducing Kelviq

Kelviq joins Subscriby as a merchant of record: it collects, handles sales tax and VAT, pays you out in 90+ countries and retries a failed renewal for you.

Introducing Polar and Mollie

Polar, a merchant of record that handles tax and pays out in 120+ countries, and Mollie, Europe's iDEAL, SEPA and Bancontact rails, join Subscriby today.

Introducing the Discord Connector

Discord is in public beta on Subscriby: one verified app grants roles, channels and whole-server memberships on payment, slash commands and recovery included.

Subscriby 5.1.0

Features

• Discord joins Telegram as a connector, in a private beta for invited creators. One verified Subscriby app is added to a server from the dashboard, with no bot to create and no token to paste; a plan can sell a role, a private channel or membership of the whole server, under one-time, recurring, pass and pass-series plans alike. A member who pays is given the roles the plan includes the moment the payment settles: added to the server by the app itself when they connected their Discord account on the portal, or handed a single-use invite otherwise; the roles go when access ends, and a server plan ending keeps the member's seat or removes them, the creator's choice.
• Members run their membership from inside the server with /subscriby: what they hold, the plans with a Buy button each, a link code, a refresh, a message to the creator, their referral code, an access code, cancellation with the creator's offer, the follow-up switch, their passes and the recovery email. Creators run the business with /subscriby-admin: projects, plans, coupons, access codes, places on sale, payment methods, broadcasts, the support inbox and the relay forum, the Referral and Partner Programs, the portal design, Revenue Recovery, Smart Links, creator tasks, the connectors, pass windows as events, Disaster Recovery, alerts and the Copilot, every answer private to them.
• On Discord a broadcast is posted once in the announcement channel mentioning the plans' roles, support is answered from the creator's direct messages or as threads in a forum channel, a member who joins the server without a membership is sent the plans once, Linked Roles let any role require a verified membership, and pass windows appear on the server's event calendar, voice and stage channels by default with a per-server default and a per-place choice.
• The Disaster Recovery Program covers Discord: the app, every place on sale and the creator's own account are probed, a standby role or channel waits per place with a live mirror of a channel's posts, a lost place is swapped by hand or by automatic failover with every holder re-admitted, and a creator proves a new or a backup Discord account through one link.
• The Telegram platform bot's project card gains four buttons: Creator Tasks with a Done button per task that issues the access and tells the member, Support Relay with the linked group and its unlinking, Connectors with the state the last probe found, and Disaster Recovery with the readiness lines and open incidents, so the bot now offers every everyday task the dashboard does.
• On the Connectors page a pending connector carries a Connect button beside its row, a connector's page lists the install steps of a connector that asks for nothing to type, and a place picked from a connector's list keeps its own name however short.
• The sidebar's Notifications Center is now simply Notifications: the entry, its flyout and the page say the one word.

For developers

• The connector SDK is 1.14.0. The Core API grows the contracts a connector's creator and member surfaces run on: Memberships, Storefront, Projects, Plans, Coupons, AccessCodes, Broadcasts, PaymentSetup, CreatorTasks, CreatorSessions and AccessWindows, with the creator-side reads of Support and Installations and the recovery handshake, mirror pairs and recovery commands on Recovery; the ports Announcer, SpaceBrowser, InstallationActions and CopilotSurface; the events AccessWindowChanged and InstallationSettingsChanged; and the ResourceSettings, CreatorLoginMethod, BroadcastHints and SupportRelayOptions slots. The SDK docs carry a page per contract.
• POST /v1/projects/{project}/resources/from-space takes a title of one character and up, so a place can be sold under the name the platform spells it; the Zapier and n8n apps follow.

Fixes

• Confirming a Copilot action on a turn that thought first no longer loses the reply: the action ran, but the answer came back as a failure saying nothing had changed. A reply that still fails after an action ran now says which action ran and that nothing was charged.
• Choosing a first plan opens Stripe's page again. The sentence meant to sit beside Stripe's button is one Stripe refuses on the billing every live plan runs under, so for a few hours every first checkout failed instead of opening; the sentence now travels only where Stripe accepts it, and the plans page says the same on its own.
• A connect that Discord completed without one of the permissions the app asks for is refused on the spot, naming the permissions as Discord's own page spells them, instead of reading Connected until the next health probe.
• A server plan ending no longer removes a member who still pays for a role or a channel on the same server.
• The marketing pages' sentences about the connector in development read right the day none is, with no edit.

Subscriby 5.0.17

Features

• Cancelling a date now asks what happens to season-ticket holders, and spells out every refund. Cancel Window opens a dialog that says who holds the date: single-date holders are moved to the next window on sale, or have their pass ended when there is none, and for season-ticket holders you choose between Move them to the next date and Drop the date from their season, so a day with no event no longer hands a weekly pass a free date the following week. Afterwards a settlement dialog lists how many were moved, dropped and ended, and every holder owed a refund decision with what they paid and what the date was worth, added up per currency; the same list reaches your notifications and email. Each holder's message now states the amounts too and that the refund is your decision. A season can no longer be deleted while a holder still has a date ahead, a moved date included, and a holder whose links a cancellation revoked gets fresh ones ahead of the new date rather than only at opening.
• Removing the "Powered by Subscriby" mark is now your choice. A Remove Subscriby Branding switch in the project editor takes the mark off your public portal page, the social card shown wherever its link is shared and your bot's messages on the Starter and Growth plans; it is off until you turn it on, so a project carries the mark until you do, and a plan that stops including it brings the mark back while the switch keeps its position. On Free the switch is greyed out under the plans that include it. The pricing page, the plan comparison and Plans & Billing say so.
• Let the storefront arrange itself. A project selling dated passes or a season no longer has to drag the current date to the top: switch on Arrange by what is happening now at the top of the Storefront Order dialog and the portal, the embed and the bot put the passes and seasons whose access is on right now first, the one ending soonest at the top, then the ones opening soonest, then everything else in the order you arranged. The dialog shows the arrangement buyers see at that moment above your own order, which still decides within each group. The switch comes with the Growth plan or the Passes Addon on any plan; if that lapses, the storefronts fall back to your pinned order at once, the setting is reset and you are told which projects it touched. Integrations read and set the same choice as the project's "storefront_arrangement" field.
• Design your portal page. Portal, a new entry of the project menu right after Subscription Plans, and the Customize button beside Open Portal open the portal designer: the banner image, the project photo, a tagline and a row of social links under Brand, and under Colours six presets (Classic, Dark, Midnight, Paper, Pastel and Bold, each with a light and a dark palette), a colour mode that paints light, dark or follows the visitor's browser, the accent, a second accent for the pass strips, the background and its grid, and the card, heading, text and caption colours for those who want them. Every change is saved into a draft the moment you make it and shown at once in a preview of the real portal page beside the controls, at desktop, tablet and phone width; nothing changes for your members until you press Publish, Discard Draft throws the draft away, and Reset this section puts one section back to the defaults. The banner and photo moved there from the project editor, which now shows a Design your portal row instead; your existing images are kept, and an image still shows on the portal the moment it is uploaded.
• Design your portal from your Telegram bot too. 🎨 Portal Designer on every project card of the platform bot opens the same designer in the chat: a home screen that says whether a draft waits and when it was saved and opens the real portal page with the draft through a ten-minute preview link, Brand for the tagline and the social links (pick the network, type the address, name a custom link, remove any with its button), and Colours for the six presets and the colour mode as buttons, every colour typed as a hex code and the grid flipped. Each change saves into the same draft the dashboard shows, so you can start on the phone and finish at the desk; Publish, Discard Draft and a per-section reset behind a question complete the loop, and the banner and photo stay on the dashboard. Integrations building their own creator surface get the same designer through the SDK's new Portal Design port and the portal_design management command.
• Set the portal's type. Typography in the portal designer, and the same screen on your Telegram bot, chooses the display face for the project's name, the headings and the figures and the body face for everything else from twelve: Asap Condensed and Inter, the pair every portal had, plus Poppins, Montserrat, Space Grotesk, Bebas Neue, Oswald, DM Serif Display, Playfair Display, Lora, Manrope and Sora, each served from the portal itself and cut to the Latin letters, so a member's browser never calls a font service. Headings can be set in capitals, as they always were, or as written, and the type scale steps the whole page one size smaller or larger with its proportions kept. A portal that keeps the defaults is byte for byte the page it was.
• Shape the portal. Shape in the portal designer, and the same screen on your Telegram bot, sets the corner radius of every card at once (sharp, soft or round, the round every portal had), the buttons members press (pill, rounded or square; filled dark, in your accent or outlined; their labels in capitals or as written), how far the cards, the dialogs and the photo lift off the page (no shadow, soft or strong) and a hairline border around the two surface cards in your heading colour. The plan buttons keep your accent and follow the button shape. A portal that keeps the defaults looks exactly as it did.
• Lay the portal out. Layout in the portal designer, and the same screen on your Telegram bot, puts the sidebar card on the left as it always was, on the right, above the plans, or above them under a full-width banner; sets how wide the page is; keeps the sidebar in view or lets it scroll away; lays the plan cards out as a list or in two or three columns, roomy or compact, with or without the heading above them; and chooses which public figures the sidebar shows, the subscriber count, the follower count or both, and the count a figure must reach before it shows. A portal that keeps the defaults looks exactly as it did.
• Every member screen now follows the design. The checkout, the membership, account and referral screens, the sign-in sheets, the Copilot bubble and the follow-up page paint their surfaces, text, lines and tints from the portal's palette, and the pass and series strips with their countdowns take the second accent, so a dark palette is dark everywhere a member goes and an accent you chose shows on every button, badge and highlight. Warnings and errors keep their amber and red. A portal that keeps the defaults looks exactly as it did.
• Write your own words on the portal. Wording in the portal designer, and the same screen on your Telegram bot, takes ten texts of yours over the built-in wording: the heading and subtitle over the plan list, the button on every plan that sells, the Login and Share buttons, the checkout heading and subtitle, one sentence of your own above the acceptance line, and the heading and a thank-you message on the success screen. A text you write shows in every language; a field you leave empty keeps the ten built-in translations.
• Say more under the plans. Blocks in the portal designer, and the same screen on your Telegram bot, adds the first content blocks to the portal page: a list of perks, what the community offers beyond the plans, each line with a tick in your accent; a card about you, with your name and a few lines; and questions and answers members open one at a time, with one tap to bring in the questions you wrote for members in Knowledge as editable copies. Each block has a heading of its own and shows only once it has something in it.
• A button and a footer of your own. Button & Footer in the portal designer, and the same screen on your Telegram bot, puts a second button of yours beside the connector button in the sidebar, a community site, a store, a booking page, with a label and an address, and fills the footer under the sidebar card: a refund policy, a contact page or mail address and an imprint beside Terms and Privacy, a line of your own under them for a company name or a registration number, and the Help link kept or hidden.
• Say it across the top. Announcement Bar in the portal designer, and the same screen on your Telegram bot, puts a strip across the top of the portal page in your heading colour, for a launch, a holiday closure or a last call: one line, a link if you want one, and a window picked in your own timezone, so the strip shows itself and takes itself down on time.
• Show and tell under the plans. Media in the portal designer adds a video from YouTube or Vimeo that loads only when a member presses play, so the page sets no cookie before that; a gallery of up to eight pictures, each cut to the same shape; and what members say, up to twelve quotes with a name, what they are and a photo if you have one. On your Telegram bot the video and the quotes are typed and the headings written; pictures are added on the dashboard.
• Your portal, in your order. Sections in the portal designer lets you drag the parts of the sidebar card (the tagline, the metrics, the buttons, the description, the social links, the footer links) and the blocks under the plans into the order you want, and switch any of them off without losing what is in it; the list of languages under the card can be hidden too. The same order and switches are on your Telegram bot, one tap at a time.
• The page around the plans, your way. Behaviour in the portal designer picks a featured plan that carries a Most popular badge in your accent, decides whether the coupon box shows on every checkout or only once a coupon arrives with the link, switches the Share and Login buttons off, shows how many members joined this week (a count only, never a name, and only from three up), hides the seats-left badge on a series, and chooses which of the seventeen share networks the share sheet offers. The same choices are on your Telegram bot.
• Seen where you want, measured how you want. Visibility & Code in the portal designer hides the portal from search engines, keeps the social card off a shared link, adds your own Meta Pixel, Google Analytics 4, TikTok Pixel and Google Ads tags by their IDs (each loads only after a visitor accepts the matching cookies in the notice, and never in your own preview) and takes a custom stylesheet of up to 16 KB that is added after the theme so your rules win. The switches and the IDs are on your Telegram bot too.
• Your card, your words. The portal's social card now paints in your design's colours, or you upload one of your own (1200 by 630) and that one is sent when the link is shared; the page title's suffix and the description search engines and shared links show are yours to write in Visibility & Code; and the plan embed from Smart Links starts from your portal's mode and accent until you pick otherwise. The title and the description are on your Telegram bot too.
• Speak your members' language first. Language in the portal designer picks the language a visitor sees before they choose one and which of the ten languages the switcher under the sidebar card offers; a visitor's own choice and a link that names a language still come first, and every portal text exists in all ten. The same two choices are on your Telegram bot.
• Colours that read. The portal designer and your Telegram bot now refuse a body text, heading or caption colour that would blend into the cards or the page, naming the two colours, so a blue on blue never goes live.
• Your portal design, over the API and from an agent. Read the published design and the draft, change any of its keys, publish or discard, and store a gallery picture, a member's photo or the card, over REST or through four MCP tools; a publish from anywhere raises the project.design_published event naming the sections that changed, and Zapier and n8n carry the same steps and the trigger.
• The portal's member counts are the designer's choice alone. The Enable Public Metrics switch left the project editor: whether the subscriber and follower figures show, and from which count, is set in Portal Designer under Layout, where it already was, and a project that had the switch off keeps its figures hidden. The project's metrics field left the API and the agent tools with it.
• Try the designer on the demo portal. The demo portal page carries the designer's panel for every visitor, opened from a tab on the right edge: every section, every option and every picture, painting the page as you go, with Save keeping it in your own browser and Discard or Reset All bringing the demo back. Nothing a visitor does reaches the demo itself.
• Your portal on your own domain. Custom Domain, the last section of the Portal Designer on the Growth plan, connects a hostname such as members.yourdomain.com: add one CNAME record at your DNS host and the certificate is issued for you; the section shows where the hostname stands (waiting for DNS, issuing the certificate, active, or what needs attention), checks it every hour or on Check Now, and tells you when it answers. Once active, every address on the portal carries your hostname, a visit to the old handle address is sent there, and a visitor who opens the hostname while your plan no longer includes it is sent back to the handle until the plan returns. Remove puts the handle address back at once.
• Members can sign in to your portal with Facebook, LinkedIn and X, beside Google. The sign-in sheet offers all four on every portal, your own domain included, with nothing to set up on your side, and Account & Recovery links or disconnects each one as a recovery method. A social button signs in a member who has linked that account; someone new is pointed to your project's connector or email first, so a social sign-in never creates a stray account. An X account that shares no email address still signs in, shown simply as Connected.
• The Copilot panel expands. An Expand button in its header widens the panel across the page to the sidebar's edge and back, gliding both ways, with the conversation held in a centred reading column so long answers stay readable; your browser remembers the width you chose. The Threads button became a compact icon to make room.
• The checkout's date picker says which date is which. When a pass is bought, the window whose access is on right now wears an Ongoing badge and the next date in line wears Next, so the current week can never be mistaken for the coming one — the mix-up that had buyers purchase last week's pass while it was still on sale for its remaining days. Every other date stays unbadged.
• The plans page now says what the card is for before Stripe asks for it. Choosing a plan, Free included, took you to Stripe's page and a request for a card against a bill of $0, with no word of why; the page now spells it out first — $0 today and every month on Free, the card is kept only so your transaction fees can be billed once a month on what your members actually pay, nothing is charged while you earn nothing, Stripe keeps the card and we never see the number, cancel anytime — and Stripe's own page repeats the same sentence beside its button. If you leave Stripe's page without finishing, the plans page now says plainly that nothing was charged and no card was saved, instead of a red warning.
• If you stop partway through setting up, one short email picks up exactly where you left off. Instead of a single "haven't launched yet" note three days in, there is now one email for each place people actually stop: your address not yet verified (a fresh link, then one more two days later), the plans page left without choosing (why the card is asked for, in five lines), Stripe's page opened and closed (nothing was charged, nothing was saved, an hour later and once more the next day), and the three steps of the tour you can stall on — no project yet, a project with nothing connected, a community connected but no plan on sale or no way to get paid — each linked to the exact page the step is taken on. Every one is sent once, never once you have moved on, and every one can be answered by replying.
• A handle of your own for your portal page, on every plan, and an old address that never breaks. Choosing the address your portal answers on used to be a Starter and Growth feature, and a creator who moved to Free had their chosen handles replaced with random ones. Now the handle field in the project editor, in the bot's project wizard (which suggests a random handle you can keep at one tap) and in Project Settings on the bot is open on every plan, Free included, and nothing takes a handle away on a downgrade. Every address a project has ever answered on keeps working: a link shared under an old handle, in a bio, on a printed code or on a bot button, sends the visitor to the current page (or straight to your own domain when you have one), including the embed, the social card and Smart Links, and the editor lists these former addresses under the handle. A handle another project has, or used to have, is refused as taken, which also replaces the error page you used to meet when you typed a handle another creator already held.

For developers

• POST /v1/projects/{project}/pass-windows/{window}/cancel and cancel_pass_window take an optional series_holders (substitute, the default, or drop); meta gains subscribers_affected, series_holders, refunds (one row per holder owed a decision with the raw and formatted amounts) and refund_totals per currency; pass.window_cancelled carries legs_dropped and series_holders and counts dropped legs in subscribers_affected. The same choice is on the Zapier Cancel Pass Window action and the n8n Pass Window → Cancel operation.
• hide_branding on POST and PATCH /v1/projects, in the project resource, on the create_project and update_project tools, in the Zapier Create Project and Update Project actions and in the n8n project operations: the Remove Subscriby Branding switch, off by default; turning it on without the no_branding capability answers TEAM_TIER_REQUIRED.
• GET /v1/me and get_me list a custom_domain capability beside the others, true on the Growth plan; the hostname itself is managed in the dashboard and travels over no endpoint yet.
• The connector SDK gains Core\PortalDesign, which hands a connector's creator surface a project's portal design: the draft beside the published design with every choice, its label and its options, the signed ten-minute preview address, a draft that names only what changed, and publish, discard and a per-section reset, every call acting as the creator under the project's permissions and every refusal a PortalDesignRefused with a stable reason. portal_design joins the management-command catalogue, and the Telegram connector declares it.
• The MCP catalogue reaches parity with the REST API: thirteen tools close every remaining gap — list_subscriptions with its status and plan filters, create_token (attenuated to the calling token, the plaintext in the answer once) and get_token, get_group, get_role and get_team_member, get_alert_destinations and update_alert_destinations, get_partner_referral, get_recovery_incident and get_recovery_operation, list_broadcast_audiences, and revoke_access_code. Every endpoint's OpenAPI operation now names its tool in x-mcp-tools; the deliberate exceptions that remain are the creator's own account security and recovery, file downloads, and surfaces no public endpoint carries.
• A monthly sweep deletes Stripe customers that never came to anything: older than thirty days, no balance, no subscription of any status and no open invoice at Stripe, and no plan behind them here. The plans page no longer opens a customer for every visitor, so the sweep clears what the old behaviour left and keeps the list from growing again; subscriby:billing:purge-empty-stripe-customers --dry-run lists what a run would delete without touching Stripe.
• The custom_handle capability is gone. GET /v1/me and get_me no longer list it, POST /v1/projects, PATCH /v1/projects/{project}, create_project and update_project take a handle on every tier (no more TEAM_TIER_REQUIRED for one), and a handle has to be unique across every project's current and former handles. A changed handle keeps the old address answering with a permanent redirect to the current one, and a blank handle is written as null. The Zapier app's Create Project and Update Project say the same; nothing changes for n8n.

Fixes

• Muted labels, dates, struck-through rows and article links across the marketing site are a shade darker, and no heading skips a level any more, so every page meets the contrast and outline that readers with low vision and the accessibility checkers expect; the home page had slipped to 97 on that check.
• Gallery pictures upload again. The Portal Designer's gallery refused every picture, because the storage that holds an upload in transit signs one file per request while the picker sent the whole selection as one batch; the picker still lets you choose many pictures at once and now carries them up one after another, with a counter and a progress bar while it works. Quote photos, the social card, the banner and the project photo were never affected.
• The home page's platform chips and payment logos load from the page itself rather than the asset server, so the performance score no longer loses points to a second connection on the first screen.
• Connecting a bot now says what went wrong. Pasting a token that already serves another project, or one the platform turns down, used to answer "Something went wrong" with nothing to act on; the connect dialog now tells you which of the two it was, keeps what you typed on screen so you can correct it, and asks for another token instead of a support ticket.
• Sections on the marketing pages no longer look broken when you move down the page quickly. Each section's illustrations travel separately from the page so the first screen stays light, and they were fetched only once you were nearly on top of them, so dragging the scrollbar landed you on a section whose artwork had not arrived yet. They now start arriving three screens ahead instead of one, and the rest are brought in while your browser is idle, so a section is complete before you reach it however fast you scroll.
• The illustrations inside the home page's feature cards keep readable contrast in every state they cycle through: the green and amber badges, the dimmed copilot lines and the muted labels are a shade deeper, and a waiting support thread is no longer faded out, so the accessibility score holds at 100 on the home page.

Introducing the Portal Designer

Design the portal page your members buy and sign in on: presets, colours, fonts, layout, blocks, your own words, pixels and a stylesheet, on every plan.

Introducing Subscriby Copilot AI

An AI operator in your dashboard and bot: it answers from your own data, does the routine work with your permissions, answers your members and writes you every Monday.

Subscriby 5.0.16

Features

• Subscriby Copilot is an operator inside your dashboard. Press Ask Copilot in the sidebar and ask about your projects, members and money in plain words, or tell it what to do: it reads your own data and runs the routine work with exactly your permissions, never more; before anything it cannot undo it shows a card with the exact arguments and waits for you to confirm, and Review every change puts the new things it makes behind a card too. Its answer streams in as it works, with the reasoning open to read and a line for every step it took and how long it was; it opens what it just made or read with one tap and ends with the next steps to tap; a thread follows you from page to page, and the Threads button brings an older one back. Beside Send you choose Auto, Lite, Pro or Max, each saying what it is for and what a turn costs. A team permission grants the Copilot to a role, and whoever asks is bounded by their own role.
• Ask Copilot from inside your Telegram bot too: Ask Copilot on the home menu and on every project card, or /copilot, opens it, and every message you type while it is open is a question; the bot shows the Copilot thinking in front of you, then answers with buttons that open what it names, up to three follow-up questions to tap and Confirm or Cancel for anything it is holding; when your Copilot Credits are spent it offers a top-up.
• Copilot Credits pay for the Copilot, and nothing else does. Every plan includes free turns each month, 10 on Free, 25 on Starter and 50 on Growth, and free member answers, 100, 250 and 500; past the free part a turn is $0.10, more past four tool steps and on Max, a suggested reply in the inbox $0.05 and a member answer $0.01, drawn from the free allowance first, then the free part of your credits, then the paid part. Packs of $10, $25, $50 and $100 are bought through Stripe Checkout, the $25 pack with $2.50 on top and the two larger ones with 15%, auto top-up buys the pack you choose when the balance falls under $5, and a monthly spend cap holds the line where you set it. Plans & Billing shows one balance with the free part and its lapse date under it, this month's usage by kind, the packs and a statement; Copilot Credits never touch an invoice and never pay for a plan, nothing is ever owed, and an empty balance stops the meter, not the free turns.
• Press ✨ in a support thread and the Copilot drafts your next reply from the conversation, the member's standing, your saved replies and your Knowledge; you read it, edit it and send it, or dismiss it, and the member never sees a draft. Each draft is $0.05 of Copilot Credits, never a free turn.
• Let the Copilot answer your members' own-subscription questions in the inbox: a switch in the inbox's settings, off until you turn it on. When it is on, a question about a receipt, the renewal date, pausing or cancelling, a failed payment or the portal address is answered at once from the member's own record, marked as an automated answer from your project and written into the thread for you to read, and everything else waits for a person as before; at most ten answers an hour on a thread, one member answer each. A member is answered by a separate assistant with no tools and no view of anything but their own standing, your saved replies, your portal address and what you wrote for members.
• Teach the Copilot about your project on the new Knowledge page, the last entry of your project's menu, on every plan and free to fill: write a question with its answer or upload a plain-text or Markdown guide, choose on two cards whether members may be answered from it (Members & Team) or only the people who run the project (Team Only), and read in What the Copilot Knows the passages the Copilot would be handed for any question, each with the entry it came from, before a member ever asks; an entry is cut into passages and ready the moment it is saved, up to 200 entries and 2 MB a file. A member whose question your Knowledge covers hears back at once from the entries you marked for them, in the inbox and your bot, with the entries the answer drew on kept on the thread; the suggested reply reads every matching passage, your team's notes included, because you read it before anything goes out. Knowledge has its own five permissions, and every entry's history is in the activity log.
• The Copilot answers your members on your portal page too. A second switch in the inbox's settings, Let Subscriby Copilot answer members on your portal, off until you turn it on, puts Ask Copilot in the corner of the page for a signed-in member: a sheet with three starter questions, answers about their own membership and from your Knowledge, marked as automated answers from your project, a button that opens their memberships when the answer is about them, Talk to a person, which files the chat on their inbox thread as a note and sends them to your bot, and nothing kept beyond the visit; one member answer each, at most twenty an hour per member.
• Every Monday at seven, in your own time zone, Subscriby Copilot writes you the week: what came in and from how many payments against the week before, who joined and who cancelled and why, the renewals that failed and the ones paid after all, who sits in a grace window or had access paused, the trials ending this week, who is waiting in your inboxes, and up to three steps worth doing, each with a button to its page; it arrives in the bell, by email and on your connected account as your alert destinations say, under a new Subscriby Copilot class you route like any other, and a week with nothing to say sends nothing. Between Mondays it reads every project against its own four weeks before and tells you once when something breaks pattern: payments failing far more often than usual, a day of cancellations, or a payment rail on which every recent attempt failed; the alert stays open while the signal lasts and closes by itself when it stops. Neither costs a turn or a cent.
• The Copilot reads what is on your screen. While the eye beside the context chip is lit, the text of the page you are looking at travels with your message, what is in view first, so "why is this one red?" or "add up this column" works on any page; tap the eye to keep it off a sensitive page, and your browser remembers the choice. What it reads counts toward the turn's tokens, never as an extra turn.
• Under every Copilot answer a small line says what it used: the tier and the model that answered, the prompt tokens with the cached part, the output tokens, the time, and whether it was a free turn or one from your Copilot Credits. A table in an answer is shown as a card per row, so nothing runs out of the panel.
• Speak to the Copilot: tap the microphone in the composer and the field becomes a recorder with a clock and a live spectrum of your voice; press ✓ and your words land in the composer for you to read and send. Tap the speaker under an answer and it is read aloud, in a natural voice for English and in your browser's own voice for the other languages. Recording and reading are free.
• Every fee Subscriby charges you is on a Transaction Fees ledger of your own. Plans & Billing gains a Transaction Fees card with the month's total, what Stripe took at source, what is billed on your invoice and what is still awaiting one, and a ledger page behind it: one month at a time, every fee as a line with the member's payment it came from and the rate applied, whether it was taken at source or metered onto your invoice, and the invoice that billed it once paid; filter by project, channel and kind, sort by date or amount, and export the month as a CSV. The fees of the months before today are filled in from your payment history.
• The home page's fonts come from the page's own host rather than the asset host; the headline font is asked for on every screen and the text font before the first paint only from tablet widths up, a phone asking for it the moment it has painted, so a desktop's largest paint no longer waits on a second host's handshake. The text a phone paints first, in the stand-in faces, now measures the same as the web fonts at every weight, so the fonts' arrival moves nothing; before, a stressed phrase in the hero paragraph jumped a line.
• The time beside a date on a coupon, a Smart Link and a hand-placed access window is shown in 12-hour time, and the pass series' Watch From and Watch Until dates open the same calendar as everything else.
• Sign in with Google, Facebook, Apple, Microsoft, LinkedIn, X or Reddit. The sign-in and sign-up pages carry a button per provider, and a provider signs you in only once it is linked to your account under Settings → Social Logins: a sign-in through a provider whose email matches your account but is not linked is refused with the way to link it, and you get an email about the attempt. A new creator can sign up through a provider: the form comes prefilled, no password is asked for, and the account starts verified when the provider vouches for the address. An account without a password confirms you through your provider wherever a password used to be retyped, and Security offers Set a Password whenever you want one.

For developers

• The Transaction Fees ledger is readable over the API: GET /v1/me/transaction-fees pages the lines with the same filters as the dashboard, GET /v1/me/transaction-fees/summary adds one calendar month up per channel, kind, project and invoice, and the MCP tools list_transaction_fees and get_transaction_fee_summary answer the same objects, all behind account:read.
• What a project teaches Subscriby Copilot is open to integrations: GET and POST /v1/projects/{project}/knowledge and GET, PATCH and DELETE /v1/projects/{project}/knowledge/{entry}read, teach, change and remove Knowledge entries, a document arriving as text, behind the project-knowledge abilities; the MCP tools list_knowledge_entries, get_knowledge_entry, create_knowledge_entry, update_knowledge_entry and delete_knowledge_entry answer the same objects; knowledge.created, knowledge.updated and knowledge.deleted announce every change without carrying the text; and a project's support settings carry copilot_answers and copilot_portal over REST and MCP, the two switches that let the Copilot answer members. The Zapier and n8n integrations gain the same steps and triggers at 4.4.0.
• Copilot Credits are readable and manageable over the API: GET /v1/me/copilot-credits answers the balance split into free and paid, this month's free allowance and usage, the per-unit prices, the packs on sale and the settings in one object, GET /v1/me/copilot-credits/statement pages every pack, grant, refund, lapse and month of usage, POST /v1/me/copilot-credits/packs opens a purchase and answers the Stripe Checkout URL to pay on, and PATCH /v1/me/copilot-credits/settings changes the auto top-up and the monthly cap; the MCP tools get_copilot_credits, list_copilot_credits_statement, create_copilot_credits_pack and update_copilot_credits_settings answer the same objects. The reads need account:read, the writes account:write. The Zapier and n8n integrations gain the reads and the settings write; buying a pack stays a page a person pays on.

Fixes

• Subscriby's own live-support chat no longer appears on a creator's public portal page, which is the creator's page, not Subscriby's.
• The label a search engine prints above every result of ours reads Subscriby rather than the bare domain: the site no longer offers its domain as an alternate name beside the brand, which had made the engine pick the domain.
• The footer's link columns and copyright line are simply there: they no longer fade in on your approach, vanish for a second when you jump to the end of a page, or seem to load in place.
• The home page's scrollbar no longer jumps as you scroll: every section below the hero reserves its own height before it is drawn, so the page is as long at the top as it is at the bottom, on phones and desktops alike.
• The sign-in and sign-up pages open faster: the dashboard beside the form is a picture of it, in light and in dark, rather than the dashboard itself being built behind the form.
• A tampered request that tries to push a file through a part of a page that takes no uploads is refused as the bad request it is and counted against its sender, the way a tampered page state already is, instead of raising a server error.
• A live dashboard update raised in the first seconds after the server restarts is retried for a few minutes instead of being dropped, and the live-update server now starts before the workers that feed it.
• The home page's hero backdrop and its premium badge come from the page's own host like its fonts, the VS mark in the menu is drawn by the page itself rather than fetched, and the Copilot card's styles travel with the card instead of in the page, so the first screen no longer waits on a second host's handshake on warm visits and the page a phone paints first is a little lighter.
• On the Compliance page every sub-processor card shows its country beside the name, so a longer description no longer runs under it, and Anthropic carries its own mark.
• A coupon's start and end and a Smart Link's end are saved at the moment you picked them in your own timezone. Before, a creator whose account timezone is not UTC saw them land shifted by that timezone's offset, and the editor showed the shifted time when it was reopened.

Subscriby 5.0.15

Features

• The home page paints sooner, on phones in particular. The dashboard preview and its sidebar arrive as AVIF images at the first paint, a third of the bytes they weighed; the illustrations of the feature cards, the six feature bands and the automations stage no longer travel inside the page but are fetched a screen ahead of you, which makes the page almost a quarter lighter; the fonts are asked for at the first paint only from tablet widths up, the site icon rides inside the page, and the cookie notice's frame is an AVIF too, so a phone's first paint waits on nothing from a second host. A browser without AVIF (Safari before 16.4) shows the cookie notice on its plain green without the frame's texture.
• The home page's scripts start in short steps instead of one long one: the hero wakes first, the header on your first move, the pricing band and the footer as you approach them, with the prices in the page from the start, so a phone answers your first tap sooner and every page's shared script is a few kilobytes smaller for a compatibility shim no current browser needs.
• The plans page and the bot's plan list say why visitors are offered nothing. A project whose only plan is access codes only, customers only, switched off, paused by the platform, a pass with no window on sale or a season with nothing sellable reads a warning above the plans list and at the top of the bot's plan list, naming the storefront (the portal, then each connected connector's installation) and the reason, instead of an active plan on the dashboard beside a portal that says there are no plans yet.

For developers

• Every marketing page says what the origin made of a dictionary request in an X-Shared-Dictionary header: off while the feature is switched off, none when the request carried no hash, no-coding when it did not accept the coding, unknown when no kept dictionary has the hash, failed when the codec or the store refused, applied for a delta. The answer is decided by the hash the browser sent, since the edge rewrites the accepted codings on the way in, and a dictionary is addressed by its own bytes, so a redeploy of the same release keeps one.
• The shared dictionary is rebuilt every hour, so a cache clear no longer leaves every marketing page answering in full until the next release; and a delta is cached at the edge only while a half-hourly probe has shown the edge keeps the delta apart from the plain page, after an edge cache key had served deltas to browsers that could not decode them. Shareable marketing pages state their byte length, which the edge's persistent reserve needs to keep them.
• The OpenAPI document the docs carry always names the public API host; the snapshot synced on 7 and 13 October had carried the exporting machine's own address and the docs' playground offered it as the server.
• Every host's robots file states its Content Signals (contentsignals.org): the marketing site, the docs and the asset host allow search, AI answers and AI training; a creator's portal allows search and AI answers but not training, a reservation made for the creator; the dashboard allows none beside closing itself to crawlers. Each file opens with the signals spelled out in words.

Fixes

• Three errors the dashboard filed most often are gone: picking a project in the sidebar threw on every pick, leaving a page through the sidebar threw from its scroll fades, and a tab left open across a release ran new markup on the old scripts; it now reloads itself at its next page change.
• In the bots, a refusal written for a person (enabling Telegram Stars on a project with no connected bot, among a dozen others) is answered in the chat as the sentence it is, with the way back, instead of an apology for an error; and a tap on a plan-wizard button from a message that outlived its draft is told that the information is missing instead of failing.
• The agent tool catalogue on marketing pages is read only once the page has fully arrived; on a slow connection it could be cut mid-way and register no tools.
• The OpenAPI document and the Postman collection export again at every start: a dependency update had changed how the document carries its webhook events, and the first start of this release failed to write either. The same update had silently dropped every response and webhook example from the regenerated document and described a handful of counts (a funnel's totals, a reminder run, a cancelled window's settlement) as always zero; both are back to what the document said before.

Introducing Revenue Recovery

Keep the members you were about to lose: a grace window when a renewal fails, one offer when a member cancels, sequences in your words, and churn analysis.

Subscriby 5.0.14

Features

• Revenue Recovery: what a project does when a renewal fails. A failed renewal keeps the member's access for a grace window you set per project (none until you set one, up to thirty days) while the gateway retries; the member is told at once, where they already talk to your project, with their payment method's own way to pay again, reminded on day three, warned the day before the window closes, and paused only when it does; the next charge that settles lets them straight back in with fresh links and counts as a recovery. A never-paid trial keeps today's immediate removal, a one-time purchase never enters grace, and the ladder stops the moment a charge settles. On every plan.
• The cancellation screen: a member who cancels on the portal or in the bot is asked why, from ten reasons and Other in their language, with an optional sentence, and then shown one offer the project makes on their rail: a billing cycle on hold where the gateway can hold the charge, a discount on the renewals where the gateway can carry a coupon, or a coupon to come back with on every payment method. Every answer, the offer shown and whether it was taken are written down; a pause ends by itself after one cycle with a welcome back. The question is on every plan; the offers need Growth or the Revenue Recovery Addon.
• Win-back sequences: up to eight messages in your words, each 1 to 180 days after the one before, with {name}, {project}, {coupon}, {discount}and {link}filled per member and an optional coupon per step, sent where the member is with the way back as a button. A member whose last live membership ended is enrolled once into every running sequence, never while they hold a live membership; a payment ends the sequence as a win and tells you. On Growth or with the Revenue Recovery Addon.
• The Revenue Recovery page in the project menu: an overview with the failed renewals, the recoveries and what they brought back, the members in grace and paused right now and the sequences' figures; the settings card with the ladder in words and a dialog for the grace window, the question, the daily digest and the three offers; a Sequences face with a sequence editor, a step editor and a preview for a sample member; a Cancellations face with why members cancel as bars, the offers shown and taken and every record with the member's own words; and an Activity face with the whole ledger. The project dashboard gains a Revenue Recovery card, the PDF, CSV, text and Excel exports a Revenue Recovery section, and the Revenue Recovery alert class carries the cancellation feedback, a sequence that won a member back and a daily digest on the days something happened.
• The project bot asks a cancelling member why and makes the one offer in the same words as the portal, and the Subscriby bot carries the creator's switches: the grace window from five choices, the question, the digest and, on a plan with the offers, the pause and the two coupons.
• The Revenue Recovery Addon ($9 a month, $90 a year) unlocks the offers and the sequences on Free and Starter; Growth includes them. A Revenue Recovery feature page on the marketing site, a row on the pricing comparison and on the comparison pages against Whop, InviteMember, BotSubscription, LaunchPass and Tribute, a question on the pricing page, and a line in the privacy policy on what a cancellation screen stores.
• Revenue Recovery before the sale: the sequence engine's three other moments go live under the same feature. A lead (a first message to your bot, a sign-in to your portal, a Smart Link or a referral link followed, without a purchase) enters a lead sequence from their first contact; every checkout a member starts on the portal or in the bot is written to a ledger and counted as stalled once the checkout window you set (one hour by default, up to twenty-four) has passed with no settled charge, which opens a stalled-checkout sequence with the plan they were buying; a trial without a card enters a trial-ending sequence the days before its end you chose (three by default, up to fourteen), and the win-back trigger leaves that member to it. A first step may go out within the hour; every step's button leads to the plan on the surface the member is reached on, the bot with the step's coupon already applied or the portal checkout with the plan and the coupon; a checkout or trial step falls back to email with a one-tap stop when no account can be reached; and every step carries a Stop that ends the follow-ups until a charge settles or the member switches them back on in their portal account. On Growth or with the Revenue Recovery Addon; the ledger and the two windows on every plan.
• The Revenue Recovery page gains a Checkouts face (every checkout with the member, the plan, the rail, where it started, when it stalled and what became of it, narrowed to the stalled or the recovered ones), the two windows in its settings dialog, a third overview row (leads arrived, nurtured and converted; checkouts started, stalled and recovered with what they were worth; trials reminded and kept) and its sequences grouped under the four moments with a starter per trigger, three steps on the right days with every word yours; the project dashboard's card and the four export formats carry the same figures. Members get a Follow-up messages switch in their portal account settings; on the project bot a step's button opens the plan with the coupon applied and Stop ends the follow-ups; on the Subscriby bot the creator sets the two windows beside the grace window. The Revenue Recovery feature page on the marketing site gains the three moments, the comparison pages against Whop, InviteMember, BotSubscription, LaunchPass and Tribute a Checkout and Lead Follow-up row, the pricing page a question, and the privacy policy a line on the follow-ups and what a checkout stores.
• Marketing pages stay cached at the edge for a week between releases instead of ten minutes, so a visitor far from the origin is served from the nearest location; a release, an article reaching its publication time and, once a day, the home page with its live figures each clear the copies they change.
• In Chrome and Edge, every marketing page after the first one you open arrives up to nine tenths smaller: the browser keeps the site's shared stylesheet and chrome once, as a dictionary, and each later page is sent as only what differs from it. The dashboard's stylesheet and scripts work the same way across releases: a browser that holds the previous version downloads the difference, a kilobyte or two, instead of the whole file.
• The dashboard preview on the home page is shorter and lighter: the subscriber, access-code, coupon and referral tables left it, the still a phone sees is served at a phone's size, less than a third of the bytes, and the still is captured whole again down to its last row.

For developers

• Revenue Recovery on the REST API under /v1/projects/{project}/retention: the settings read and written (GET and PUT, every field optional, null clearing an offer), the figures over a period preset with the reasons members gave, the cancellation screens paged by reason and surface and the activity ledger paged by kind, behind project-subscription:view, view-any and update. Win-back sequences under /v1/projects/{project}/sequences behind the new project-sequence:view-any, view, create, update and delete abilities and team permissions: list with counts and filters, create with the steps in one call, read, update (the steps replace the whole list in order and keep the ids still in place), delete, and the enrolments of one sequence by the way out.
• Eleven MCP tools: get_retention_settings, update_retention_settings, get_retention_stats, list_cancellation_feedback, list_retention_activity, list_sequences, get_sequence, create_sequence, update_sequence, delete_sequence and list_sequence_enrollments. Twelve webhook events: subscription.payment_recovered, subscription.access_suspended, subscription.access_restored, subscription.cancellation_feedback and subscription.offer_taken, and sequence.created, sequence.updated, sequence.deleted, sequence.enrolled, sequence.step_sent, sequence.converted and sequence.exited, the sequence family behind project-sequence:view.
• The Zapier app and the n8n node, both 4.3.0, carry the twelve triggers, the eleven operations each, and the Revenue Recovery and Sequence resources; the docs carry a Revenue Recovery guide, a members' page on a failed payment, the addon page, the two tool groups and the API references.
• Connector SDK 1.8.0 adds the Core\Retention port (the cancellation screen for a member with its reasons and the one offer, the feedback recorded, the offer taken or declined) and the Core\RetentionManagement port (a project's settings read and saved as a one-field draft), so a connector's member and creator surfaces run the same screens and switches as the portal and the dashboard.
• Lead nurture on the REST API: the Revenue Recovery settings carry checkout_stall_hours and trial_notice_days, the figures carry the nine nurture counts with the recovered checkouts in US dollars, GET /v1/projects/{project}/retention/checkouts pages the checkout ledger with each checkout's outcome (open, stalled, recovered, completed) and its filters, the sequence writes accept all four triggers and a first step at 0 days. Three webhook events: member.lead_created, checkout.stalled and checkout.recovered. One MCP tool, list_checkouts, beside the widened retention and sequence tools. Zapier and n8n 4.3.0 carry the three triggers, Find Checkouts and List Checkouts, the two settings fields and the four trigger choices. Connector SDK 1.8.0's Core\Retention port grows recordCheckoutStart(), arriveFromSequence() and stopSequences(), and RetentionManagement's draft and details carry the two windows.

Fixes

• The home page no longer keeps a phone busy while the features band is off screen: its flowing dashes animated in a way the off-screen pause could not stop, which cost phones most of a second of layout work on every visit.

Introducing the Subscriby Partner Program

Refer creators to Subscriby and earn 5% to 30% of every invoice they pay for 12 months, as Subscriby Credit or cash. They get 20% off their first 3 months.

Subscriby 5.0.13

Features

• Smart Links: one tracked address per channel. Create a link for each place you promote a project (a video description, a bio, a printed flyer, a newsletter, your own website) with a name, the word that ends the address, a destination (your portal, one plan or your bot) and an optional expiry. Every click is counted once per address per link per hour; a visitor who signs in within thirty days is credited to the last link they clicked, a member who starts your bot through the link's deep link is credited at once, and a member who has ever paid keeps their source, so revenue never moves between links. The utm_source, utm_medium and utm_campaign tags on an arrival are kept with the member. On every plan, including Free.
• The Smart Links page in the project menu lists every link, live and archived, with its address, destination, lifetime clicks beside a 30-day chart, leads, checkouts, paid members, conversion, revenue in USD and state, closed by a Direct row so the figures add up to the project's totals; the row menu views, edits, copies the web address and the bot link, opens the history and archives (an archived link keeps its figures and stops counting). The detail flyout carries the web and bot addresses with copy buttons, a QR code with an SVG download that keeps working after the address is renamed, four funnel tiles, the revenue per currency, the click chart and the last members the link brought, linking to the members page filtered by that link.
• Embed on Your Website: two pieces of HTML to paste into any site you run, a button that opens your portal and your plan cards framed in the page, light or dark with one accent colour and the button's words of your choosing, with a live preview. A card's button opens the checkout on that plan in the visitor's own window and credits the link; nothing is loaded on your site but the frame, and no analytics cookie is set.
• Members and subscriptions carry a Came From row (the link, the door they came through, the date and the campaign tags, or Direct) and both lists gain a source filter; the project dashboard gains a Where Members Come From card and the PDF report a Smart Links table.
• The Overall dashboard gains the same Where Members Come From card across every project you own or share: each link names its project, the Direct row pools the members no link brought anywhere, and the Attribution figures cover them all.
• On a project's bot, a Smart Link's deep link credits the member in silence and opens the plan the link sells, or the home screen; on the Subscriby bot the project card gains Manage Smart Links, listing each link with its lifetime clicks, members and paid members and opening one link's destination, funnel, conversion, revenue per currency and addresses.
• A Smart Links feature page on the marketing site, a Smart Links row on the pricing comparison and on the comparison pages against Whop, InviteMember, BotSubscription, LaunchPass and Tribute, and the home page's features band gains a Smart Links card and a Partner Program card, while its Beautiful Dashboard card becomes Dashboard, API and MCP: the same action done from the dashboard, over the REST API and through an AI assistant, with the live counts of resource families, webhook events and MCP tools, and a Webhooks & Events card shows the signed events arriving at an endpoint.

For developers

• Smart Links on the REST API under /v1/projects/{project}/links: list with an archived switch and a search, create, read, update, archive (a delete that archives), the project funnel with its Direct row and totals that add up, and one link's funnel, behind the five project-link abilities; every link carries its three addresses and its state. Members and subscriptions gain source (the link, the door, the campaign tags; null for a Direct member).
• Six MCP tools (list_links, get_link, create_link, update_link, archive_link, get_link_funnel), three webhook events (link.created, link.updated with the changes, link.archived), three Zapier triggers, three creates and three searches, and an n8n Smart Link resource with the three trigger events; the docs carry a Smart Links guide and the tool pages.
• Connector SDK 1.7.0 adds the Core\SmartLinks port: a member's arrival through a link's code, a creator's links with their funnel, and one link by id, so a connector can credit an arrival and show a creator their links without reaching into the application.
• The embed page is the one response any site may frame: it answers with a Content-Security-Policy that allows every frame ancestor and without X-Frame-Options, hides from search engines, sets no cookie and may be cached for a minute.

Fixes

• On the home page the floating navigation turns white as it passes over the dashboard preview and over the footer, and frosts again on the way back up, with the same transition it already had; over a dark surface the frosted glass read as a grey smear.
• The footer's wordmark holds its place near the bottom of the window while the footer scrolls through and settles into the hills, fog at first and blurred while the link columns pass over it; the columns themselves arrive with the scroll, the outer two first, then the rest.
• The quarter-hour Disaster Recovery probe asked each creator's plan once per channel or group it checked, so an account with many places cost hundreds of reads a run; it now asks once per batch of places, the way the reconcile sweep and the connector probe already did.
• A bot token that already serves another project is answered in words on the platform bot, with the token prompt kept open for another token, instead of a generic failure that quoted an internal message and asked the creator to contact support.

Subscriby 5.0.12

Features

• The Partner Program: bring creators to Subscriby and earn on every invoice they pay. Apply from the new Partner Program page in the sidebar (who you are, where your audience lives and how large it is, the promotion you commit to, how you expect to be paid), get approved by a person, and share your partner link or code. A creator who signs up through it gets 20% off their first three months; their first paid Starter or Growth invoice converts the referral, and every invoice they pay for twelve months earns you a commission, held thirty days, then payable as Subscriby Credit on your own invoices or in cash once a month from $50 by PayPal, Wise, Remitly or USDT, less the rail's transfer fees.
• The commission is a ladder. Every partner starts at 5%; each commitment you made on your application (a long-form video review on your YouTube channel, a short video on TikTok, Instagram or YouTube, a comparison article or a case study on your blog or Medium, your partner link in the public description of a community you run) is tied to one of the audiences you declared and adds its points the moment we verify the proof you submit from the page, scaled by that audience's size (nothing below 10,001 followers, half from there, the full points above a million); 10 and 25 paying referrals add 5 points each, and the rate is capped at 30%. Only work anyone can see counts. A raise reaches every creator still earning you a commission; verified work that later vanishes or goes private has its points withdrawn, the rate goes back down and commissions not yet paid out are recalculated.
• A partner can add a commitment they did not make on their application from their Partner Program page, on an audience they declared or a new one above the reach floor, with the proof due 60 days later; the ladder alone sets the rate, which is never negotiated.
• The Partner Program page shows your link, your code and a deep link per connector, link clicks, creators referred, conversions, commission earned, payable and settled, every referral with its state, the commission ledger, your payouts, your commitments with their due dates and proof, and the payout details dialog with the terms, the rail, the legal name and the tax residence. The Overall Dashboard gains a Partner Program card, the export a Partner Program section, and the billing plan card names the Subscriby Credit on your account.
• The Subscriby Telegram bot carries the programme too: a 🤝 Partner Program button on the home menu shows the terms and the way to the application, or, once you are approved, your code and links with a copy button, the sentence to share, your rate broken down, your referrals, commissions and payouts, your commitments with a Send Proof button and a way to add one later, the payout-details conversation and the terms to accept; a creator who opens the bot through your partner link and creates their account in the chat is recorded as your referral.
• A sign-up that looks like the partner themselves (the partner's own card at conversion, their own network, an alias of their email, too many sign-ups from one link in a day) is recorded and held for review rather than refused, earns nothing until Subscriby decides, and never tells the partner it was caught.
• A Partners page on the marketing site explains the programme, the ladder and what the other platforms pay, and a visitor who arrives through a partner link sees the offer on the home page; the Partner Program Terms are a new legal page, and the privacy and cookie policies name the partner cookie and what a partner can see about the creators they referred.
• The pricing page answers whether Subscriby has a partner program, and the comparison pages carry a row on it against Whop, InviteMember, BotSubscription, LaunchPass and Tribute.

For developers

• Ten partner.* webhook events announce a referral signed up and converted, a commission earned, approved, credited and reversed, a payout recorded, an application approved or rejected and a rate change, all behind account:read; their narrative and payloads are in the webhook reference.
• The Partner Program is on the REST API under /v1/me/partner, behind account:read and account:write: the standing (the application's state, the code and the links once approved, the commission ladder, the referral tallies, the balances, the payout rail and whether it is complete, the tax declaration, the terms and every commitment with its proof state; never the destination a rail pays to), the referrals, the commission ledger and the payouts paged, the payout details written and the terms accepted; GET /v1/me carries partner_code and partner_link once approved. Six MCP tools do the same: get_partner_program, list_partner_referrals, list_partner_rewards, list_partner_payouts, update_partner_payout_details and accept_partner_terms. The Zapier app and the n8n node, both 4.1.0, carry the ten partner.* triggers and the same operations.
• Connector SDK 1.6.0 adds the Core\PartnerProgram port a connector's creator surface reads the programme through (the standing in the core's words, the ledgers paged, the commitments and their proof, the payout rails and the terms), CreatorRegistration::$partnerCode for a sign-up a deep link opened, and the partner_program management command.

Fixes

• The closing call-to-action card on every blog article stacked its heading into four lines beside two floating buttons; it now lays out as text, then buttons, at every width.
• Search engines are handed the square brand emblem as the logo (the wordmark fell under the minimum size), a one-sentence description of the company and the site's domain as its alternate name; the home page's description names the product, and every share image carries an alt text.
• The question lists on the marketing pages are well-formed definition lists again, so the accessibility tree an AI agent navigates reads each question with its answer; the weekly site audit now checks every definition list for that shape.

Subscriby 5.0.11

Features

• A Referral Program for every project. Members join it from the portal or the bot and get a code and a link; a friend who signs up through them and pays earns the referrer free membership days or a cash commission you set, as a percentage of every payment for a number of months or for life, or a fixed amount on the first payment. First touch wins for thirty days, a friend who arrives through a link is counted the moment they sign in, and a member who has ever paid cannot be referred. Included on Growth, or as the Referral Program Addon at $9 a month or $90 a year on Free and Starter, the same footing as coupon codes.
• The Referral Program page sits under Coupon Codes in the project menu: an overview with the program in words and six figures, affiliates to approve, suspend, enrol by hand or pay, every referral and its state, the reward ledger, payouts with a CSV export, and the settings in a dialog that creates the program on its first save. You choose who may join (anyone, or paying members only; approved by you, or at once), what referrers earn, what friends get (one of your coupons applied at checkout, days on their first membership, or nothing), which plans count, how long a commission is held behind your refund window, the payout details affiliates leave, and your own terms. A full refund reverses a reward or claws it back from the next; days are never taken back. The members flyout shows Referred By and Referrals Made.
• Members see Refer & Earn in the portal's account menu and on My Memberships while a program is live: the offer in your words, one button to join, their code and links with copy buttons, how many friends they referred and how many paid, the days they earned or their commissions on hold, payable and paid out per currency, the payout details you asked for, stored encrypted, and the program's terms. The checkout gains a Referred by a Friend? box under the coupon box, which applies the friend's coupon at once, for a typed code and for a link arrival alike.
• Affiliates are told the terms in words. The approval notice states what they earn and for how long, what their friends get, how long a friend who arrives through them stays theirs and when a commission becomes payable, then your terms and their code; every approved and pending affiliate hears again, by chat and by mail, whenever those terms change, when the program is paused and when it resumes. Rewards already earned keep their figures.
• An affiliate's payout details, their answer to the question you set with a cash commission, now show wherever you pay: in the affiliate's flyout, in the Record a Payout dialog, in a Pays Out To column on the Payouts tab and in its CSV export.
• Both dashboards gain a Referral Program card beside Coupon Codes: the affiliates who brought the most paying friends in the selected period, with their standing and what each earned, and Referral Impact with friends referred, friends who paid, rewards earned and what is payable to affiliates right now. The dashboard export and report carry the same figures.
• The billing page's plan card names the next renewal date and the addons riding on the subscription.
• The home page answers what Subscriby is, which platforms it works with, how creators are paid and what the free plan costs, in a question block beside the documentation link.

Fixes

• Webhook endpoints received every event twice, as two deliveries with different event ids, because the step that fans an event out to endpoints was wired up two ways. Each event now reaches an endpoint once. Nothing else was affected: the second copy of every other internal follow-up found its work already done.
• A failed sign-in no longer drags the dashboard preview beside the form out of place. The helper that scrolls the first validation error into view looked for red text anywhere on the page and found the preview's red trend arrow before the form's own message; it now looks only inside the form that failed.

Connectors

• Refer & Earn on the Telegram project bot: a 🎁 button on the home screen and the subscription card while a program is live, the offer in your terms, Join the Program, the member's code with a Share with Friends button and their Telegram and web links, a friend who opens a referral link counted before the home screen draws, and a friend's referral code accepted at the bot's coupon prompt.
• The Referral Program is run from the Telegram platform bot too. Manage Referral Program on the project card sets the program up in a few answers (what referrers earn, what their friends get, who may join, whether you approve each affiliate, the hold and the payout question on a cash commission, your own terms), shows it in words with its figures, changes one setting at a time, pauses, resumes and deletes it, lists affiliates by standing, approves, suspends and enrols them from a member search, and records a payout against what is payable, by a typed amount or all of it.
• On the project bot, an affiliate on a cash program answers your payout question under 💳 Payout Details on their Refer & Earn screen and can clear it again; only you can read the answer.

For developers

• Fifteen endpoints under /v1/projects/{project}for the Referral Program: the program read, saved (the first save creates it), activated, deactivated and deleted; affiliates listed, read with their per-currency balances, enrolled by member id, approved and suspended; referrals and the reward ledger listed with typed filters, the referrals list taking a since instant; payouts listed and recorded up to the payable balance; all behind five new project-referral token abilities. Fifteen MCP tools cover the same actions, ten referral.* webhook events each carry a Zapier trigger and an n8n trigger, and both integrations gain the referral actions.
• Connector SDK 1.5.0: a ReferralManagement contract on the Core API for a connector's creator surface (the options a setup needs, the program read and saved from a draft, switched on and off and deleted, affiliates listed, read with their balances and payout details, approved, suspended and enrolled from a member search, payouts recorded), updatePayoutDetails() on the Referrals contract with the payout question on the program summary and the answer on the affiliate's standing, and a referral_program_manage command in the management catalogue and the manifest schema.

Documentation

• The creators' Referral Program guide, the subscribers' Refer a Friend page, the Referral Program Addon page, the referral family in the REST, MCP and webhook references, the Telegram bot guide's Refer & Earn section and the Referrals port in the Connector SDK's Core API.
• The Referral Management port and the Referrals port's payout details in the Connector SDK's Core API, the management command catalogue, the Telegram bot guide's creator section and Refer & Earn notes, and the creators' and subscribers' referral pages.

Subscriby 5.0.10

Features

• Everything an account holds can be downloaded from Settings → Profile: the account itself and, for each project, the plans, members, memberships, payments, coupons, dates and support conversations, as a spreadsheet per project and as JSON files in the shapes the API publishes. One export builds at a time and one may be asked for a day; the link in the email works for a day and the archive is kept for a week, and because it holds members' personal data the email says to keep it safe.
• Deleting an account no longer happens the moment it is confirmed. The deletion is scheduled a week out, the export of everything the account holds is built and emailed first, a banner names the date on every dashboard page, and signing in and choosing "Keep my account" cancels it. On the day the projects, the members' memberships and their payment history are deleted as before, and a final email confirms it.
• A creator on a yearly plan is emailed thirty days before it renews, with the amount about to be charged, the renewal date and how to cancel, so there is time to decide before the charge; monthly plans are unchanged.
• A browser that sends the Global Privacy Control signal is taken at its word: analytics and targeting cookies stay off, the cookie notice shows those choices greyed out with a line saying why, and a sign-up from such a browser is reported to no advertising platform, whatever was chosen earlier.

Performance

• A creator's portal looks its project up once per page instead of a dozen times: every read of the project and of the signed-in member during a render used to go back to the database, two queries each, so a portal with a long plan list spent its time repeating one lookup.

Fixes

• The calculator page no longer opens dead in Firefox. Its component was registered by a script tag that could run after the page's own bundle had started, so every figure on the page failed to resolve; the bundle is now loaded through the same loader as the rest of the site, in order.

Connectors

• The Telegram checkout's welcome screen names Subscriby's Terms for Members beside the creator's own terms button, so a member has seen both documents before tapping Agree & Proceed.

For developers

• POST /v1/me/export asks for the account export and GET /v1/me/export reads the latest one, with a signed download link while it is ready, behind the new account:export token ability; an agent does the same through request_account_export and get_account_export, and the build is one more job get_job_status can follow.

Legal

• The Privacy Policy and the Terms describe the week's grace before a deletion, the export that precedes it, the renewal reminder and the Global Privacy Control signal; every legal page is dated 7 October 2026.

Documentation

• Delete account, Profile and Exporting data are rewritten around the export and the grace period, the creator subscription page explains the renewal reminder, and the API and MCP references carry the two new endpoints and tools.

Subscriby 5.0.9

Agents

• On Chrome 149 to 156 the marketing pages switch WebMCP on through Chrome's origin trial, so an agent driving the visitor's browser finds the site's tools without a flag, and the audits that list them apply instead of passing the pages by. The tools are asked of the document's model context first, the name the specification settled on.
• The cookie notice's three forms describe themselves to an agent as well, so one can keep only the essential cookies, accept all, or save a choice per category on the visitor's say-so.

Performance

• On a slow connection the fonts can arrive after the page has painted. The text now waits in a fallback cut to each font's exact measure, so when the real font arrives no line changes and nothing below the hero moves; a cold first visit used to shift the hero's buttons and backdrop by a line as the fonts swapped in.
• The header, the hero and the connector strip take their first measurements only after the browser's first paint, so the page's first layout is never forced inside the page's script, whichever of the stylesheet and the script arrives first.
• The marketing site's stylesheet travels inside each page instead of as a separate file from the asset host, so the first paint no longer waits on a second connection: a page is about 35 KB heavier on the wire and paints about a second earlier on a slow phone.
• On phones the dashboard still's sidebar is fetched at the size it is drawn, a quarter of the file it used to take.
• On phones the page's script is fetched once the first screen has painted rather than ahead of it, so the first screen is measured by what it paints with and nothing else; a desktop loads it with the page as before, where it reveals the dashboard preview.
• The cookie notice's frame artwork travels inside the page instead of being fetched, so on a first visit it is painted with the first frame rather than once a second connection has delivered it.
• The dashboard preview and its still take their scale from the browser's own size report instead of measuring themselves while the page boots, and the connector strip does the same, so a desktop's first layout is no longer forced inside the page's script.
• The gold word in the headline is offered as AVIF, a third of the size, for browsers that take it; the WebP stays for the rest.
• The hero and the cookie notice are drawn only once their markup has fully arrived. On a slow connection the browser used to paint the page while it was still streaming in, so the mountains appeared at the top of the screen and then dropped away and the notice grew in place as the rest of the page landed, a layout shift PageSpeed scored heavily right after a deploy.
• The page's first measurements wait for a layout the browser has just finished instead of the frame after the first paint, so while the hero's entrances animate no measurement forces a style recalculation.
• The chunks a bundle imports are fetched together with it instead of after it has arrived, one round trip less on the request chain.
• The hero backdrop has a 420-pixel rendition for phones that draw at one device pixel per CSS pixel.
• A rendered marketing page is kept at the origin for the same ten minutes the edge keeps it, so a visitor reaching an edge location without the page, or the first after a deploy, waits for a lookup instead of a render; the measured speed stops swinging with the edge's state.
• The home page lays out only the hero and its neighbours at first; the sections further down are prepared as they come within half a screen, so the first screen is ready sooner on slow devices and the page no longer spends over a second laying out what nobody has scrolled to yet.
• The pricing section and the footer are prepared the same way, which takes another quarter off the home page's first layout.
• The hero's mountain backdrop ships as AVIF at every size for browsers that take it, a third smaller than the WebP, which stays for the rest; the first screen's hints name the AVIF with its type so no browser preloads a file it will not paint.
• The six creator cards beside the home page's hero on wide screens appear with the hero itself, more than a second earlier than before, and glide into place without stutter.
• A phone no longer downloads the pictures and the font that only the desktop layout shows: the hero's platform icons, the gold word in the headline, the comparison glyph in the menu and the condensed italic face.
• Sections further down the home page no longer run their entrance animations backwards and out of sight the moment they are prepared; they move only when you reach them.
• The shimmer on the gold word in the headline no longer costs the browser work on every frame.
• On phones the platform strip under the headline scrolls with a lighter touch, which saves battery and keeps it smooth.
• The site icon is a lighter file.
• On phones the page's scripts now wait for the first text to be painted before they download, so the first screen arrives sooner.
• The dashboard preview under the hero fades in without costing the browser work on every frame.
• The hero's platform icons load after the text, fonts and backdrop of the first screen rather than competing with them.
• The steps band below the hero and the calculator are prepared only as you approach them, like the bands further down.
• The fonts the pages download are a third smaller: they carry only the typographic features the pages use.
• On phones the steps band's headings are set upright, so the phone's first screen no longer waits for the italic face.
• A phone no longer downloads the error reporter on every visit: the connector strip's first layout tripped a harmless browser notice that was treated as an error, and the reporter it fetched discarded the notice on arrival.
• The hero's backdrop is preloaded on tablets and up alone; a phone draws it a screen down and fetches it as a normal picture, so its first screen's downloads are its own.
• The header's menu no longer slides aside once the page's script arrives: the account buttons are drawn with the page for a visitor, a signed-in browser is recognised before the header is laid out, and the comparisons glyph keeps its box empty rather than showing a clipped word while it loads.

Marketing site

• On laptop screens between 1280 and 1600 pixels wide the header's menu is set a size smaller, and on the narrowest of them the agent badge steps aside, so the menu no longer runs into the logo on one side and the sign-in buttons on the other.
• Below 1600 pixels the passes strip under the hero spans the hero column again; the cap that keeps it clear of the creator cards applies only where those cards are drawn.
• The comparisons glyph in the header's menu keeps its height before the page's script runs, so the menu no longer nudges a few pixels as the page loads.
• The menu's in-page links (Features, Comparisons, Cases, Pricing) and a page opened on a fragment land on their section on desktops again; the browser's own smooth scroll was cancelled where the hero pins its card and stopped 2,000 pixels short.
• The hero's headline, paragraph and buttons rise in without the blur they used to clear, so their entrance runs on the compositor instead of repainting every frame for its first second.
• On phones the hero's buttons sit as close under the capability pills as the pills sit under the paragraph; the pills' row used to carry 20 pixels of extra room below.

Housekeeping

• The report-only security policy header, which enforced nothing and reported to no one, is gone, and with it a kilobyte and a half from the first response of every connection.

Subscriby 5.0.8

Features

• The cookie notice is a slim bar along the bottom of the page instead of a tall card in the corner: a frame of colour blobs around a white card, the choice buttons in one row, a close mark that keeps only the essential cookies, and the category list opening inside the same bar on Customize.
• The cookie notice on the marketing site offers a Targeting category beside Analytics, holding the Meta Pixel's two cookies, and each measurement category appears only when its tag is configured. Nothing loads before you choose, and the site stays the same page for everyone.
• Registrations and the first paid plan are now counted by the advertising and analytics platforms we measure the site with, for creators whose browser accepted the matching cookies and for no one else. The Privacy Policy, the Cookies Policy and the Compliance page say exactly what travels and when.

Performance

• On a desktop the home page's dashboard preview appears the moment the page is ready, fading in as before, instead of waiting almost two seconds, and its picture is requested with the page, so the largest paint of the first screen lands with the first screen. Phones keep the staged entrance, where the card sits below the first screen.
• The cookie notice's frame artwork is requested with the page, so a first visit on a phone paints the notice as soon as the page shows.
• On phones the header's Agent Native card is folded by the page itself rather than by its script, so on a slow connection it no longer flashes open over the hero, shifts the layout as it folds or counts as the first screen's largest paint.
• After every release the first pages, in every language, and the files they preload are fetched through the edge before anyone asks for them, and again every ten minutes, so the first visitor after a release no longer pays for a cold copy.
• A release now refreshes only the pages at the edge; pictures, fonts and scripts keep their year-long copies, so the first screen after a release is served from the edge as it was before it.
• The header and the chat launcher no longer measure the window while the page boots, which took the browser's first layout out of the boot task, up to a fifth of a second on a phone.
• The hero backdrop on phones picks its 720-pixel rendition instead of the 1366-pixel one.

Fixes

• Leaving a page while one of your changes was still saving no longer raises an error in the browser error reporter when the server's answer arrives: the answer is dropped, because the page it was meant for is gone, and the address of the page you moved on to is left alone.
• The cookie notice is a dialog on a plain container instead of an aside, which accessibility checks and AI agents' accessibility trees accept, and the phone menu bar is named by its visible text, Open menu or Close menu, instead of a label that said something else.

Marketing site

• On phones the header is two panes, the logo and the Agent Native badge above a slim Open menu bar; the menu opens from under that bar to the foot of the screen with every page on one row and a line on what it is for, and Login and Get Started side by side. As you scroll the home page the header takes a lighter shade of the section beneath it, the change riding the curve of the ribbon passing under it in either direction; elsewhere it turns white, and a tap on the badge opens its card right in the header. Opening the menu folds its bar away and raises a Close bar to the foot of the screen while the pages fade in one after another.

Documentation

• Every MCP tool in the documentation now has a page of its own under its group, as every REST endpoint and every webhook event has had since 5.0.7. A group's page keeps its overview and lists its tools, each row opening the tool's page; the sidebar shows each tool with its kind, whether it reads, writes, destroys, reports or polls, in the colour the tool lists use, and the tool's page carries that same badge beside its name. Each group page used to hold every one of its tools in full, the largest of them close to a megabyte and a half; the largest tool page is now under nine hundred kilobytes.
• A link to a tool's old place on its group page still lands on the row that leads to its page, and every link in the documentation and the Subscriby reference pages points at the tool pages directly.