Subscriby-এ নতুন কী

Subscriby 5.0.7 : Every endpoint and every event on a page of its own

Documentation

• Every REST endpoint and every webhook event in the documentation now has a page of its own under its group. A group's page keeps its overview and lists its endpoints or events, each row opening the page; the sidebar shows each endpoint with its HTTP method and each event with the webhook mark under its family, and the event families sit in one alphabetical list without the group headings they used to sit under. The single pages had grown past the two megabytes a search engine reads before it stops, so none of them was indexed in full; the largest page of the reference is now under a megabyte and a half.
• A link to an endpoint's or event's old place on a 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 new pages directly.

Subscriby 5.0.6 : Agents find their way in, and the calculator explains itself

Features

• A free fee calculator at /calculator replaces the two tool pages: two sliders for members and price, and a leaderboard that ranks thirteen tools by what each charges for the same month, counting only what the platform itself charges, so bring-your-own-gateway tools carry no processing figure. The tools that hold your money carry a lock, and a card below spells out how each pays out.
• Under the chart, the calculator names the tools ranked above Subscriby at the current sliders, each with the plan its figure comes from, the platforms it serves and the one trade-off behind its lower price; a card beside them states Subscriby's published terms, every platform with its status and the standing facts of every plan, from the exclusive passes and Disaster Recovery to the public roadmap. The summary says what share of the month you keep against the average tool, and an eighth question answers why the other tools' comparison charts leave Subscriby out.
• Hovering a leaderboard row shows its note in the site's own tooltip bubble instead of the browser's balloon; the lock, the euro mark and each platform icon explain themselves the same way on hover or focus.
• Every comparison page's pricing card links into the calculator, and the comparison index lists each tool as one full-width row: name, platforms, who it suits, the dated link to the full comparison, and a sheet of starting price, fee, revenue cap and automation.
• The Common Questions block on every marketing page is an editorial list: a heading column that stays put while the numbered questions and their answers scroll beside it.
• The home page's calculator and pricing bands end in the dark pill the Automations band uses instead of a text link.
• A client, a crawler or an AI agent handed nothing but the domain can now find everything machine-readable: an API catalog at /.well-known/api-catalog (RFC 9727) lists the REST API and the MCP server with their specification, documentation and health endpoints, every marketing page advertises the catalog, the OpenAPI document, the documentation site and llms.txt in its Link header, and the robots file states Content Signals that allow search, AI input and AI training for every bot.
• Three more well-known documents describe the agent surface: an A2A agent card at /.well-known/agent-card.json that names the MCP server as its one interface, with both ways to authenticate and one skill per group of tools; an MCP server card at /.well-known/mcp/server-card.json with the endpoint, the protocol versions, the OAuth metadata and the live tool and resource counts; and an agent-skills index at /.well-known/agent-skills/index.json whose three SKILL.md files teach the REST API, the MCP server and webhooks, every figure in them read from the running application. The authorization server also answers /.well-known/openid-configuration with its OAuth metadata, and every discovery document, the OAuth metadata and the registration endpoint can be read from any origin, so browser-based clients and validators see them.
• The MCP server states the deployed release as its version in the handshake instead of a fixed 1.0.0, the same number this changelog names.
• Every webhook delivery now carries a Web Bot Auth signature beside the shared-secret one: Signature-Agent, Signature-Input and Signature headers signed with an Ed25519 key, so a receiving endpoint, or Cloudflare in front of it, can confirm a delivery came from Subscriby without knowing the endpoint's secret. The public key is published, signed, at /.well-known/http-message-signatures-directory on the main domain.
• The fee calculator's Markdown answer carries the ranked chart for the members and price in its address, with each tool's plan and total and what is kept with Subscriby, so an agent that asks it a question gets the figures and not only the page's copy; without an address it shows the page's defaults.
• The marketing site registers tools with a WebMCP-capable browser, so an agent driving the visitor's browser can read the current page, read or open any site page, read a comparison with another tool and run the fee calculator, each answered as Markdown; a browser without the API loads nothing extra.
• An auth.md walkthrough at /auth.md on the main domain, the API host and the MCP host tells an agent in plain words how a credential is obtained and used: the discovery steps, the three ways in, where each credential works, the error envelope and how a credential is revoked. The third way is new: an agent registers itself by naming a creator's email address, shows the creator the six-digit code it is handed, and collects a personal access token for the creator's team once the creator has typed that code on a signed-in page. The token carries only the abilities the agent asked for, every read ability and no write when it asked for none, and the page lists them before the creator confirms. The authorization server's metadata advertises the registration in the profile's agent_auth block. Nothing is granted before the creator confirms, a code lasts ten minutes and allows five attempts, and a registration lapses after thirty minutes. The protected resource metadata now also names the resource and the bearer method, as the standard recommends.
• An AI capability manifest at /.well-known/ai-catalog.json, in the Agent Resource Discovery format, lists every machine-readable document Subscriby publishes with the questions each one answers, so an agent that reads one file knows where everything else is: its root lists the two cards and the three skill files and points at a second catalogue of the other documents, the shape the format asks for, and every marketing page links it from its head.
• Every marketing page carries the Agent-Native badge beside the logo, the mark Cloudflare's agent-readiness scan awards at its top level; hovering it shows the level awarded, and clicking it opens the Agent Readiness page of the documentation in a new tab.
• The marketing header knows when you are signed in: Login and Get Started give way to Logout and Dashboard, in the header bar and in the phone menu, and Logout ends your session from the marketing site in one click.
• The marketing site publishes an AGENTS.md briefing at /AGENTS.md (the surfaces, the three ways to a credential, the rules every surface shares, what needs a human, and where every longer document is) and a Markdown sitemap at /sitemap.md; every marketing page is also served as Markdown at its own address with .md appended, carrying front matter with its title, description and canonical address, naming the page as its canonical in the Link header and ending with a link to the sitemap. The MCP server card names the server at its top level the way a registry listing does, every page links the documentation glossary, and the OpenAPI document is served minified, the same document at under half the bytes.
• Every marketing page is also served as Markdown: a client whose Accept header prefers text/markdown receives the page's text instead of its layout, built from the same catalogues as llms.txt for the pages written from them and converted from the page itself for the legal pages, with an estimate of its tokens in the headers. Browsers keep receiving the page as before.
• The fee calculator compares like for like on request: seven chips above the chart (direct payouts, unlimited sales, an API and webhooks, more than one platform, a free plan, disaster recovery, time-limited passes) each hide the tools that lack it, the remaining rows close up and renumber, every statistic is read over the tools still shown, and the rank line says how many remain and why. Nothing is on by default, so the ranking by price alone that the page opens on is unchanged, each chip's tooltip says how many tools it would hide, and the explainer under the chart lists beside every cheaper tool the chips it fails. On wide screens the chips fill the chart's width in two rows.
• Every rival row of the fee calculator now says how much more or less it costs than Subscriby for the same month, in dollars and as a share to two decimals, tinted rose when it is more and green when it is less, in a last column on wider screens and under its figure on a phone. The Platform, Processing and Payout columns are gone; the charges behind each figure now sit beside the tool's name in the colours of the bar's legend, each with a tooltip that names its terms and this month's amount.

Fixes

• The home page's live preview is ready sooner on the first mouse move: its script, stylesheet and markup are now fetched quietly once the page has loaded and read back from the cache when the preview opens, where the earlier background requests were refused on the way and the first move had to download them all.
• The home page's hero no longer declares a second main landmark, the two calculator figures are no longer empty headings while the page loads, the checklist in the sales animation is a list in markup, and every image declares its size so nothing shifts as it loads; none of it changes how the page looks.
• The fee calculator's sliders move smoothly: the chart is ranked once per notch instead of once for every figure that reads it, and the page's address is updated when a slider rests rather than on every notch, which browsers had started to refuse mid-drag.
• Between phone and desktop widths the fee calculator's leaderboard puts each tool's bar on its own line under the name, so the bar is wide and no name or figure is cut short; the per-charge breakdown beside each name appears only where the row has room for it.
• The pricing page's phone layout sits in a box clipped to the sheet's rounded shape, so the plan switcher no longer paints square corners over the dark hero, and the comparison labels balance their line breaks instead of leaving one word alone.
• The Cookies Policy's definitions have a small gap between each term and its definition.
• The BotSubscription comparison credits its API where it said there was none, and notes that it covers less than Subscriby's and has no Zapier or n8n.
• In the project editor, the portal-link preview follows the handle you type again on iPhones, where every control in the editor had stopped responding after an image upload.
• The chat widget's frame no longer trips the browser error reporter, which had raised an error on every page that loaded the chat.
• A purchase whose plan has since been deleted still reaches the feed broadcast, and the purge of expired access codes no longer fails on the codes of a deleted plan.
• Error responses that point at the documentation link to the versioned pages again.

Documentation

• The API guide's Agent Readiness page covers the catalog, the agent card, the server card, the skills index, the OpenID Connect alias, the auth.md walkthrough and the agent registration it now offers, the AI capability manifest, the Web Bot Auth key directory, the WebMCP tools and the Markdown every page answers with; the MCP and REST authentication pages explain how an agent registers itself for a creator to confirm; the webhooks guide's signature page explains the Web Bot Auth signature on every delivery, and its retry page names the API routes that retry one dead delivery, replay the recent ones and pause or resume an endpoint, which it said did not exist.

Subscriby 5.0.5 : The live preview waits for your first move

Performance

• The home page's live dashboard preview now loads on your first move, scroll, touch or key on a desktop instead of in the first two seconds of every visit: a still of the same render stands in until then, the preview's files are fetched quietly after the page has loaded, and a visit nobody touches never pays for the preview at all. On a slow desktop that was most of the page's blocking time.
• The scrolling strips measure themselves a frame after they are built, so their layout happens in the frame rather than being forced inside the task that built them.

Fixes

• The live dashboard preview renders again on wide screens: its stylesheet had compiled without every Flux utility on the build server, so the mock came apart after the 5.0.4 release.
• The pricing band's prices and its two Try Free buttons are in the page from the start again, so a reader, a crawler or an accessibility audit that never scrolls sees them; the buttons' labels no longer depend on a script.
• The live preview holds nothing a keyboard can reach: its Light/Dark switcher is two plain blocks that behave like the segmented control they replace, and the mock's calendar controls are taken out of the tab order once they exist.
• The site's content security policy no longer names the retired domain, which serves nothing but a redirect.

Subscriby 5.0.4

Performance

• Every marketing page loads a stylesheet of its own, about a third of the size of the one the dashboard needs, so pages paint sooner on every connection; the dashboard is unchanged.
• The live dashboard preview on the home page loads only on screens wide enough to show it: phones and tablets no longer download its scripts, styles or markup, and the home page itself is a fifth lighter for everyone.
• The home page's sections initialise as you approach them instead of all at once on arrival, and its animated bands stay still until they are on screen, so the page answers scrolls and taps sooner.
• The support chat loads on your first move, scroll or keystroke on a desktop marketing page, and not at all on a phone, where its bubble is hidden; a button that opens the chat still fetches it on demand.
• Error reporting on the marketing pages downloads only when a page raises an error, so a visit that goes well fetches none of it; the dashboard keeps its full reporting.
• The marketing pages are held at the network edge for ten minutes and served from it for a day while they refresh in the background, so a page never waits for the server, an outage at the server shows the last good page instead of an error, and a new release is purged into view the moment it is deployed.
• A marketing page's stylesheet, scripts and fonts come from the page's own address instead of a second host, saving a connection before the first paint; the connection to the image host is opened ahead of time, and the home page names its hero image and its display italic before the page is parsed.
• The marketing fonts are cut to the letters, symbols and weights the pages set, half the bytes before the first text paints; every other glyph is fetched only by a page that needs it, so nothing renders differently.
• On wide screens the home page's mountains are held at the bottom of the window from the first paint instead of a moment after the page's scripts have run, which removes the home page's only layout shift, and the headline starts rising the moment the page paints rather than 200 ms later, so the largest thing on the page is on screen almost as soon as the first thing is.

Features

• The cookie notice answers without leaving the page: accepting, or choosing categories, closes it in place, a page you return to never shows it again, and analytics start only after you have consented and touched the page. Consent is stored in a new form, so you may be asked once more after this release.

Marketing site

• Every marketing page reads in all ten languages below the headline: the long bodies of the eight payment-method pages, the five feature pages, the five integration pages, the four switch guides, the twelve creator-type pages and the twelve comparison pages, more than 1,400 strings, are translated by hand with every platform, gateway and count placeholder kept, so a German, Hindi or Sinhala visitor no longer meets English past the headline.
• Five feature pages under /features: time-limited passes, pass series, the Disaster Recovery Program, standby bots with automatic failover, and the Member Support Inbox, each with a facts strip, four reasons, five steps, who it is for, the pages it goes with, five questions and the documentation one click away. Every figure a page quotes (the plan a feature is included on, the addon and its price, the recovery allowance and cadences, the grace and undo windows, the per-email fee, the pass window bounds, the support event and tool counts, the throttles and limits) is read at render time from the code that enforces it. The index groups the pages and says plainly that these are the features only Subscriby provides.
• Five integration pages under /integrations: Zapier, n8n, Make, Claude and AI agents through the MCP server, and the REST API with its webhooks, in the same shape, with the event, resource, ability and tool counts, the per-token rate limits, the webhook retry ladder and the idempotency window read from the code that enforces them. The Zapier page says invite-only and not yet listed, as the documentation does.
• An Automations band on the home page, under 'One Membership. Every Platform.', links to the integrations: beside the copy, an event card throws an orb along a curved dashed rail to one illustrated device at a time while the camera glides with it (an email whose flap hinges open, a spreadsheet that grows a row, a team chat, a phone, a receipt, a wall display with cheering hands, a smart speaker, a Smart disco light that turns into a Smart emergency light when a renewal fails, and Claude reached over the MCP server with a typed transcript and a reply). Six chains cycle through, each stop reporting what it did, and a header bar names the event for the whole journey. No automation platform is named inside the scene; the copy beside it names them.
• A migration hub at /switch with one guide per tool a creator might be leaving: InviteMember, BotSubscription, LaunchPass and Whop. Each guide says what you keep, what changes, how long it takes and what it costs from the live plan figures, walks the seven shared steps beside the tool's own specifics, answers five questions and links the matching comparison and the documentation's migration guide. The index states the honest premise: no tool can take over another tool's live subscriptions, so the method is one billing cycle side by side with a code-only bridge plan so nobody pays twice. Every comparison page links its switch guide.
• The comparison hub at /vs is an honest alternatives list: four method cards (grouped, not ranked; prices from the vendor, dated; where a rival beats us we say so), the tools in three groups listed alphabetically with Subscriby inside its own group marked 'That's us' and its limits stated, each entry with who it is best for, the price from, the fee, the revenue cap, API and webhooks, a standout and a watch-out, a glance table of all of them, and a question answering whether Subscriby is the best option on the page with 'not for everyone'. Every comparison page shows the date its rival's prices were checked. The MemberBot and Substack comparisons are withdrawn.
• An About page at /about (what Subscriby is and how it works in three steps, six principles, the founder, where to find us) and a Press page at /press (the brand files with their colours and usage rules, short and long boilerplates with word counts, a fact sheet with copy buttons), both in the sitemap and in llms.txt.
• The footer is a directory of the whole site: five equal columns of twelve one-line links read from the same catalogues the pages come from (features, payment methods, integrations, switch guides, comparisons, creator types, company and legal), the Sri Lanka badge and the four social profiles as labelled buttons in its header row, and the landscape kept under a still wordmark that the links clear at every width. Instagram is gone from every profile list and the X profile is labelled X (Twitter).
• A connector's public page is its search landing page: a connector may carry a title, description, headline, subline, prose sections and questions in its listing, translated in the connector's own languages, and the page shows the connector's name as its headline, the sections after the capability matrix and the questions as compact cards in the sidebar, each block rising into view as it is scrolled to. The Telegram connector's page now leads with 'Telegram Membership Bot for Paid Channels and Groups'.
• The marketing site publishes llms.txt and llms-full.txt at its root, built on request from the same catalogues the pages render, so the files can never say what the site does not: an index with one line per page and its search description, and a full file with every page's text, every comparison's side-by-side table, the whole pricing table, each connector's overview, the ten newest releases and every published article.
• The release notes on /changelog name no framework, library, vendor or developer artefact: 116 older notes were rewritten to say what changed for a creator or a member, and notes that said nothing a user could see were dropped.

Legal

• A Refund Policy at /legal/refunds in the Terms of Service format (The Gist, definitions, charges by the platform, refunds of those charges, payments by members to creators, members, termination, changes, contact), reading the trial length and the support address from the live configuration. The Terms' 'Prohibited Uses' clause becomes 'Acceptable Use' and gains the trading-community condition, the connected platform's rules, the Disaster Recovery Program's four fair-use rules and where to report; the Compliance page's DPA section states each party's role under data-protection law and what the agreement covers, and its DMCA section says what a notice must contain and what follows it.
• Terms for Members at /legal/members, written for the people who buy access from creators rather than for creators: who does what, your account, buying access, cancelling, refunds and disputes, your conduct, your data, what we cannot promise, reporting a creator, liability, changes and contact. The portal's Terms link and the bot's Terms of Service button fall back to it whenever a project sets no terms of its own. Both pages are linked from the footer, listed in llms.txt and carried in all ten languages.

Search engines

• A weekly audit renders every page the sitemaps list and reads it the way a crawler does: the status, the title and description lengths, one heading, the canonical address, the language links, image alternative text, any placeholder left unfilled, a listed page asking not to be indexed, and the share card. Anything new since the last run is reported to error monitoring. Its first run found, and this release fixes, eleven roadmap connector pages listed in the sitemap while asking not to be indexed, two home-page images without alternative text and a comparison-hub description over the snippet length; every marketing title now fits a search snippet and every description fits under 160 characters in all ten languages.
• A creator's portal tells search engines to skip it until there is something to buy: while the project is closed, offers no active plan or takes payments only through gateways in test mode, the page asks not to be indexed, which is how a demo portal's test-card instructions had sat in the index for months. Its search description is the first 155 characters of the project description cut at a word, and portals are never listed in a sitemap.
• The marketing site's robots file names the sixteen AI search and training crawlers in groups of their own, each allowed everything, so a crawler that reads only its own group sees the site's stated policy rather than inheriting whatever the general rule says that day.

Blog

• Eight more guides are scheduled, one a week from 7 December 2026 to 25 January 2027, each 1,000 to 1,750 words with a question section: InviteMember alternatives and how to switch without losing members, accepting Paystack for a paid group across Nigeria, Ghana, Kenya and South Africa, Razorpay and UPI for a paid channel in India, native in-app payments versus cards for channel access, selling a day pass or a season pass, what to do when your bot is banned, USDT and crypto payments for a signals group, and how to price a membership. Every plan figure, fee, limit and gateway fact is the one the site and the documentation state.
• The scheduled paid-channel guide answers the price-change question the way the product behaves: a new price reaches existing members at their next renewal, and the deactivated-plan renewal switch is the way to keep early supporters on the old one.

Fixes

• A pass or a pass series redeemed with an access code is no longer born cancelled. Generated codes carry a no-renewal mark so an ordinary membership never renews, but the pass pipeline read that same mark as a holder who had cancelled: the purchase dropped out of the current list, the bot's link message and the portal fell silent, and the window never admitted the join request, so a member held an invite link nobody delivered. Redeeming a code on a pass now clears the mark and generating a code for one no longer sets it.
• The processing cost of an invoiced platform fee is metered on purpose and billed with the next cycle, and the billing page says so.
• A share card's cached image is keyed by the deployed release as well as by its lines, so a deploy redraws every card; the layout fixes of 5.0.3 had kept serving the previous drawing for a day because a deploy replaces the server but not its cache.
• No comparison page calls the Zapier integration official any more: the MetricGram, SimpleSub and BotSubscription pages say Zapier and n8n integrations, in all ten languages, because the Zapier app has never been promoted to the public directory.
• The connected nav bar's tint and blur grow with the scroll distance instead of switching on at the first pixel; a phone's address bar holds the page a few pixels from the top after a scroll back up, and the tint drew a pale rectangle over the dark hero until it settled.
• The Disaster Recovery fair-use paragraph runs the full width of its card instead of stopping two thirds across; the automations scene's room devices read in sentence case (Smart speaker, Smart disco light, Smart emergency light); the Organization address in the structured data reads suite 86612; and a placeholder written with the wrong syntax in several language files is corrected.

Interface and copy

• The marketing pages read better to a screen reader and a low-vision reader: the menu button has a name and says whether it is open, every blog card's link is named after its article, the fee calculator's sliders are labelled, two headings that skipped a level are in order, and the brand green under white text (the roadmap bubble, the cookie notice's buttons, the connector status labels and the price suffix) is darkened to the nearest shade that reads at 4.5:1.
• On laptop-sized screens the home page's hero no longer shows the six creator cards beside the headline: their positions are drawn for wide monitors, and below 1600 px they overlapped the caption and the feature chips.

Subscriby 5.0.3

Marketing site

• One page per payment method under /payments (Stripe, PayPal, Paystack, Razorpay, Skrill, CoinPayments, CeyPay and the connected platform's own in-app payment) and a /payments index that says which methods renew, where each works and how to choose. Whether a method renews a plan, runs in test mode or syncs plans, and how many currencies it settles in, is read from the code the checkout enforces, so the pages can never drift from it. The home page's payment logos and the gateways each creator-type page recommends link to them.
• Every marketing page has its own share card, drawn on request in the hero's design from the page's headline and subline, so a comparison shared on social media previews as that comparison. The card's lines are measured with the renderer's own font metrics and centred above the footer, with the subline running to four lines when there is room.
• The comparison hub at /vs and the creator-type hub at /for carry an intro, a six-point checklist and five questions beneath their cards; a new comparison, Tribute, with every rival figure read from the vendor's own pages; the TGMembership comparison follows the rival's rename to BotSubscription, and the old address redirects permanently in every language.
• A public changelog at /changelog with every release back to the first commit, the product announcements woven in by date, twenty entries a page, an Atom feed at /changelog/feed and a footer link; the changelog and blog listings paginate with Newer and Older pills and round page chips in the site's own language.
• The 24 comparison and creator-type pages and both hubs carry their title, description, heading, subline and every question and answer in all ten languages, with the platform words filled after translation; the payment-method pages join them.

Blog

• An Atom feed at /blog/feed carries the twenty newest articles with their banners, announced from every marketing page's head.
• Nine guides for 2026, one a week from 5 October to 30 November, lead platform-neutral in their titles and addresses and name the platform as the worked example; every article's title and description fit a search snippet, and the blog index says what the blog covers, in ten languages.

Performance

• The marketing site is served without a session and marked cacheable at the edge for every visitor: the header's sign-in link is decided in the browser from a marker the dashboard sets on login, the locale cookie is written by the browser, and the dashboard's interface scripts no longer load on marketing pages.
• A phone's home page shows a still of the dashboard preview instead of 2,846 live elements scaled into a thumbnail, with the sidebar pinned as the live preview pins it; the page falls from 9,530 to 3,298 elements and its largest paint from 7.6 to 5.0 seconds in emulation, while a desktop keeps the live preview.
• Inter is served as a Latin subset (171 KB instead of 344, the italic 189 instead of 379) with the full font kept behind a unicode range for the scripts it carries; the early-hints header names the bundle the page runs and no longer pushes the italic fonts or the dashboard bundle onto marketing pages; the brand mark's paths are drawn once per page. A phone's transfer for the home page falls from 1,755 to 1,215 KB.

Fixes

• Both Atom feeds answered a server error to every reader in production because of the way the server read their XML declaration; the declaration now comes from the response, and a check refuses any template that could bring the problem back.
• The logo vanished from the header and footer on phones: the brand mark's symbol was defined inside the dashboard preview's inert template, which a phone never instantiates; every layout now defines it right after its body tag.
• The hero's connector strip flashed on iPhones as the page scrolled back to the top: the strip rebuilt itself on every resize event, which iOS fires when the address bar shows or hides; it rebuilds only when its width changed.
• The generated sitemaps are no longer shipped with the code, so a fresh deployment stops serving the pre-cutover files naming the beta host until its first sitemap run, and the IndexNow job remembers what it last announced across deployments rather than on a disk a deploy replaces.
• The pricing page's plan tabs on a phone are a pill again; the tab button carried two class attributes and browsers keep only the first.
• The All Projects page's loading skeleton mirrors the live table again: a name link, a Team badge, a Connectors badge, a square project image, a Connection badge, the portal link, the created time and the Active badge, at the widths the live columns take.
• On phones the menu button of the floating nav ran off the right edge of the pricing, comparison, creator-type and changelog pages: the sheet those pages sit on drew its fade overlay as a box wider than the card, so the page laid out wider than the phone and the browser zoomed it to fit. The overlay is now painted outside the card the way a shadow is, adding nothing to the page's width; a long route in a changelog note wraps instead of widening the page; and a browser test measures every page family on a phone viewport.

Interface and copy

• The passes ticket under the home hero is hidden on phones; the footer's Company column reads Blogs, Changelog, Roadmap and Status.
• The rival counts quoted on the comparison pages (webhook events, MCP tools, REST resource families, team permissions, gateways) are read from the code that defines them, and the Subscriby tiers on those pages come from the live plan rows.

Subscriby 5.0.2

Billing and plans

• The dashboards do the upgrade sum for a creator below the top tier: a fee outlook card shows this cycle's transaction fees, names the next tier as the "Subscriby Starter Plan" or "Subscriby Growth Plan", and shows the fees it would have saved as a figure of its own. Its three columns align, its sentences say what they mean, and its button reads "See Available Plans". A once-a-cycle email says when the tier above already pays for itself.
• The cancel modal states what cancelling actually does: the date the plan stops, the bundled features and add-ons that end, the limits and the fee that change against the Free tier, the portal handles that revert, the fees still to be invoiced, and that projects, members and payments stay. The Close button reads "Keep my plan", the dialog is wide enough to read, and its seventeen strings ship in ten languages.
• After a tier move, the billing page quotes the price the invoice charges: the subscription webhook reads the coupon back from Stripe with the discounts expanded, so the locked-in price is recorded.
• A plan on sale is pushed to the gateways by the action that writes it, so publishing a draft, or creating or saving a plan over REST, MCP or an integration, no longer leaves it without a Stripe price. A start link to a draft says it is not on sale instead of opening a checkout the gateway refuses.

Connectors

• A connector can be reserved for a platform tier: Slack, Zoom and Google Drive from Starter; WhatsApp and Microsoft Teams from Growth. Installing below the tier is refused with the plan it needs, under the existing CONNECTOR_TIER_REQUIRED code. The tier shows as a "Starter plan" or "Growth plan" chip on the public directory and in-app marketplace cards, as a Plan row and in the pricing box on both detail pages, in ten languages.
• A roadmap connector's page asks search engines to follow but not list it until real copy lands.

Passes

• A season's preview opens at the next pass instead of the dates already behind it, on the portal card and in the bot. The passes already run are counted in a line above, the "more passes" line counts what is left after the ones shown, and a pass running right now leads the preview.

Pricing page

• A pricing page of its own at /pricing carries the one complete plan comparison: eight sections and sixty-odd rows read from the live plan catalogue and the product's own settings; sticky price cards that keep name, price, fee and button when stuck, in compact spacing; a billing-cycle toggle that flips every figure; a stacked phone layout; a Connectors section that reads every shipped and roadmap connector from the catalogue and shows a dash under a plan that cannot install one; Time-Limited Passes and Pass Series as two labelled rows sharing one value; addon cells shown as a price block ("+$19/mo" or "+$190/yr"); and a card-grid FAQ that also replaces the accordion on the vertical and comparison pages. The home cards and the in-app plans page link to it.

Marketing site

• Every frontend hero takes the pricing page's dark treatment: the twelve vertical and twelve comparison pages and their indexes, the connectors directory and detail pages, the blog index and articles, and the four legal pages, which gain a hero for their title and last-updated line. The white sheet that overlaps a hero fades into the page from halfway down.
• The home page's title is "Membership Bot for Paid Channels & Groups — Subscriby" and names no platform, because the product runs on connectors rather than on one platform. The home and pricing titles and the structured-data names read the brand from configuration.
• The comparison pages quote catalogue counts (gateways, webhook events, REST resource families, abilities, MCP tools) from the code that defines them and build Subscriby's tier rows from the plan rows, so no figure can go stale again. The Zapier integration is no longer called an "official app", processing fees are named as the gateway's own, and the rival facts are as of 2026: InviteMember's codes, branding and gateways per plan, Memberful's single Standard plan, Ko-fi Gold at $12, LaunchPass Basic unable to charge, and BotSubscription's eight-step scale under the TGMembership name.
• The blog article's closing call to action is a dark card with a lime button and a pricing link, in ten languages.
• The chat bubble loads on the first pointer, key or touch, or after idle time within five seconds, instead of with every page.
• The fixed nav renders its colours server-side and toggles them without fading, so nothing flashes on load; its white text yields to dark when the mobile menu opens over a dark hero; the phone's sticky plan bar keeps a constant height. Row labels on the pricing table carry a dotted underline that turns solid on hover. The home page's Questions marquee sits close under the compare link again.

Blog

• Every article carries a byline and shows an "Updated" date once a revision lands a day or more after publication. The author is emitted as an Organization node linked to the blog, Open Graph carries article:published_time, modified_time and section, and an article without a banner falls back to the site card instead of failing.
• Localised copies of an article name the English address as their canonical and declare no alternates, because articles exist in English only. A category page carries its own title, heading and description in ten languages, and an article's fallback description ends on a word.

SEO and structured data

• The home page's structured data stops claiming a rating no visitor can see, prices its offers from the live plans as unit price specifications, and the site description names no single platform. The home, blog and legal pages stop emitting meta keywords.
• The Organization node carries the company's legal name, founding date, founder, postal address and support contact, read from configuration, and lists only the profiles that exist: X, LinkedIn, GitHub and Facebook.
• Every sitemap entry carries a real modification date or none; the blog's entries drop their locale alternates; blog category pages join the sitemap; the comparison and vertical indexes describe their pages as an ItemList; the legal pages carry one title each; the generated sitemaps are no longer shipped with the code.
• IndexNow: when a marketing address changes, the sitemap job announces exactly those addresses to Bing, Yandex and the other IndexNow engines, never the whole site. The key is INDEXNOW_KEY, served at /{key}.txt.
• Every public host answers its own robots.txt; the dashboard host tells crawlers to index nothing through X-Robots-Tag; sitemaps are served with an hour's cache instead of a year's.
• /index.php, a path behind it and a trailing slash answer a 301 to the canonical spelling; the spelled-out default locale (/en) redirects permanently; an error page no longer claims a canonical address, an og:url or a breadcrumb.
• The retired domain redirects to https whatever scheme the server sees behind the proxy, so links from the old domain land on the new site instead of a plain-http 404.
• Marketing images state their width and height before the bytes arrive; the hero word mark and the blog banners above the fold ask for high fetch priority; connector logos lazy-load by default, load eagerly in a hero, and carry the connector's name as alt text; creator avatars in the hero are named by their creator. The exchange-rates strip and the cookie banner are marked data-nosnippet, and the two italic font files lose their preload.

Dashboard

• The Acquisitions vs Cancellations chart fills its card beside the ranked revenue list on wide screens.

Under the hood

• The plan sync resolves each gateway handler through a typed method.
• AWS SDK and related packages updated to their latest versions.

Subscriby 5.0.1 : The contract release

Features

• The connector contract release: the first connector's legacy columns and the invite-token pivot are gone, every read answers from the connector rows, and the connector SDK ships as 2.0.0. Nothing changes for creators or members.
• An All Transactions ledger with search, sort and filters, linked from every Recent Transactions card; a cash flow card beside the portfolio; a calendar tile on every transaction and recent-subscriber row; Revenue per Plan as a ranked bar list.
• A downgrade warns which chosen portal handles it will replace and sends the new links; a member is found by the account they connected, over REST and MCP; the platform bot's command menu is a catalogue in code and every entry answers.
• The OpenAPI document carries the bearer scheme, the error envelope, paging, and the ability, events and MCP tools of every operation; every REST resource family and every webhook family is documented end to end with real examples; every documentation link carries its version segment.

Fixes

• A fresh verification link is one click from the sign-in page and from an expired link, links live a day, and a typed address is lowercased instead of refused; the sign-up email stops at its first failing rule.
• Every bot button fits the platform's 64-byte callback limit, so the project card, the plan's resource picker and the paged lists answer again; "Sign in with Telegram" answers again.
• The quarter-hour sweep issues the access a purchase never received; a season is reissued one date at a time; opening a date no longer withdraws the next one's link; a removal's ban expires on its own; deleting a project withdraws its installations.
• The API answers CORS preflights in full; a missing row is a 404, never an error report; a duplicate plan name is a field error on every surface, never a 500.

Interface and copy

• The connector sign-in methods fold into one pane above the form; the register button reads "Create My Subscriby Account"; the marketing pages, comparison tables and legal pages speak the connector family; five home-page mocks rebuilt as larger animated scenes; the passes ticket restyled.

Under the hood

• The runtime, the web framework and the billing, spreadsheet and payment libraries move to their current major versions; reminder ladders and sweeps stream per chunk; the reconcile sweep asks about each live grant once a day.

Subscriby 5.0: Connectors. One Membership. Every Platform.

Subscriby 5.0 rebuilds the platform around Connectors: Telegram first, Discord next, plus an SDK and marketplace so one membership spans every platform.

Subscriby 5.0.0 : Connectors

Overview

• Subscriby is now connector-based. A project installs connectors; Telegram is the first official connector, and everything Subscriby does for a Telegram community today it does through that connector. Nothing changes for existing creators or members on upgrade: every project, bot, member, invite link, pass and wizard keeps working as before.

Highlights

• Connectors Marketplace, on the website (/connectors) and inside the app: Available, Experimental, Under Development and Coming Soon lanes, official badges, New and Trending chips, a detail page per connector with Overview and Configuration tabs, and a Notify-me list on roadmap connectors. Discord is under development; Slack, WhatsApp, Microsoft Teams, Discourse, Ghost, Google Drive, GitHub, Reddit, Guilded and Zoom are on the roadmap.
• A Connectors page per project: install, connect, verify, configure and disconnect a connector; switch its capabilities on or off per project (messaging, broadcasts, support relay, built-in payments, recovery); run the Connector Doctor for a verdict on every gated place; uninstall with an impact preview, and Restore Access after reinstalling.
• Connector outages and Outage Compensation: when a platform refuses a project's bot, dependent plans go off sale everywhere and the creator is told; when the outage ends, the lost time is banked on every affected purchase and everyone hears about it. Growth projects are health-probed every 15 minutes and can fail over to a standby bot automatically.
• Notifications Center: every creator alert kept in an inbox with a bell that moves, on the dashboard, REST and MCP.
• Analytics by connector on both dashboards, REST and MCP; a ranked portfolio leaderboard on the overall dashboard.
• Email-first creator accounts with linked connector accounts; per-class alert destinations; members' connected accounts on the portal with "Notify me here" per account.
• Telegram Stars is a payment method the Telegram connector provides; a project can hold one native payment method per connected connector.

Reliability

• A platform re-sending an update after a timeout is handled once.
• An operator can pause a connector during an incident: its webhook answers "retry later", outgoing messages wait until it resumes, probes and reconciliation skip it, and the dashboard shows it as Paused. Nothing is lost.
• Access grants are reconciled against every gated place every fifteen minutes.
• Disconnecting a project's bot no longer removes the project's members, subscriptions or resources.
• Relinking a bot to a new token keeps its installation, outage ledger and linked identities.
• Webhooks now fire for projects that belong to no team. Before, payment and membership events on those projects reached no endpoint at all.

Dashboard and portal

• Subscriptions show whether a member joined the places their purchase unlocks ("Joined", "1 of 3 joined"), cancelled renewals read "Access continues until …", and the subscriber's billing email is shown.
• The Resources page offers one tab per kind the project's connectors gate; nothing can be added until a connector is connected; "Manual" perks read "Manual Perk".
• The Disaster Recovery pages render once per installed connector, in that connector's words.
• Member notices route by intent: access notices on the platform the access is on, support replies where the member wrote from, receipts and reminders on the member's preferred account, email only when nothing else reaches them.
• The dashboard, emails and API refusals say "connected account" and "connector" where they used to name one platform, in all ten languages.
• Sign-in and sign-up offer "Continue with …" per connector that signs creators in.

Integrations: breaking changes

• The bot-shaped surface is removed. Existing webhook subscriptions and API tokens are migrated at deploy, so nothing goes silent; new Zaps and workflows must use the connector names. New Zapier, n8n and MCP majors ship with this release.
• Removed: GET / DELETE /v1/projects/{p}/bot. Use instead: GET / DELETE /v1/projects/{p}/connectors/{key}/installation.
• Removed: GET /v1/projects/{p}/distribution/bot-link. Use instead: GET /v1/projects/{p}/distribution/start-link?connector=.
• Removed: bot_id on project create and update. Use instead: POST /v1/projects/{p}/connectors/{key}.
• Removed: MCP get_bot_status, disconnect_bot. Use instead: get_connector_installation, disconnect_connector.
• Removed: Webhooks project.bot.connected / disconnected / status_changed. Use instead: connector.connected / disconnected / status_changed.
• Removed: Abilities bot:manage, platform-telegram:admin. Use instead: project-connector:*.
• Removed: telegram_user_id on members. Use instead: identities[] (connector, external id, display name, username, preferred, notify).
• Removed: Resource type, chat_id. Use instead: kind (manual or connector:kind, e.g. telegram:channel), connector, space {id, external_id, title}.
• Removed: ?type= on the resource list. Use instead: ?kind=, ?connector=.
• Removed: Health reasons telegram_api_*. Use instead: connector_api_unauthorized / not_found / rate_limited / error.
• Removed: Payment method provider platformcurrency. Use instead: telegram:stars; payment methods carry connector.
• New surfaces: GET /v1/connectors, GET /v1/projects/{p}/connectors, installation verify and uninstall preview, GET /v1/me, /v1/me/identities, /v1/me/alert-destinations, /v1/me/notifications, GET /v1/subscriptions/{s}/grants and grant reissue, creator tasks, the full Disaster Recovery family on REST and MCP, and the webhook events connector.*, recovery.*, member.identity_linked / identity_unlinked, member.resource_pending / resource_failed / access_extended, creator_task.*.

For developers

• Connector SDK 1.0.0 (subscriby/connector-sdk): the manifest (connector.json), the ports, the Core API a connector calls back into, the conformance kit, and a Fake connector as the reference implementation.
• Building Connectors docs: a full reference (manifest block by block, one page per port and per Core API contract, the conformance kit rule by rule, testing and publishing) and a ten-chapter tutorial.
• Zapier and n8n docs are generated from the integrations themselves, and both builds fail when a Subscriby endpoint or event has no counterpart.

Fixes

• Photos and files members send to the support inbox open again.
• The Connector Doctor asks about a channel through the installation that administers it, so a healthy channel no longer reads "chat not found".
• The Built-in payments switch is enforced; Account recovery reads Always On on a project installation.
• A creator's project list keeps one order, so the bot's project picker stops shuffling.
• A closing season date no longer races its own hand-off; invite links are scoped to their pass window.
• Invoice events from the platform's billing provider are handled again and billing.invoice_paid is emitted once per invoice.
• Every Paystack event after the first charge reaches its subscription; a webhook's signing method resolves once the parked checkout expires.
• Places linked in the same second keep one fixed order in the Restore Access report, the uninstall preview and the resource list.
• The portal sidebar no longer raises a deprecation for a project without a description.

Upgrade notes

• Nothing for creators or members to do. The release ships as two deploys days apart: 5.0.0 adds the connector tables and runs a one-off backfill of every existing bot, chat, resource and invite link into them; 5.0.1 removes the old columns once the nightly verification has been green for the chosen number of nights.

Subscriby 4.1.0

Features

• Season lounge resources with validation for linked rooms; cryptocurrency exchange rates, formatting and minimum prices improved; the plan editor's Resource Access section reorganised.

Fixes

• Resource binding in the plan editor.

Subscriby 4.0.3

Features

• Storefront order management for plans with a sales cap per plan; the series timetable in the bot; compact date ranges for pass windows; unknown commands handled and standby chats probed; bot health probed one job per bot; Telegram invoice titles fit their limits.

Fixes

• Scripts embedded in pages are escaped safely; "Prevention is part of the Growth Plan" reads the same everywhere; the readmitted count on the home page; backlog queries handle many projects in one request.

Subscriby 4.0.2

Features

• A platform metrics service aggregates and caches platform-wide figures.

Fixes

• The live mirroring message reads the same in every language; home page colours for the flexibility and safety sections.

Subscriby 4.0.1

Fixes

• PayPal acknowledges webhook events it takes no action on; dashboard rows without a creation timestamp render.

Introducing the Disaster Recovery Program

Subscriby detects a lost Telegram account, bot or channel in seconds and moves you to a new one while every paying member is re-admitted automatically.

Subscriby 4.0.0 : The layered rebuild

Features

• The REST API and the MCP server reach parity with every dashboard verb, and webhooks announce resource, payment method and support writes.
• The support inbox relays through a Telegram group with topics end to end; webhook endpoints enforce allowed IPs and CIDR ranges at delivery; a rate-limited broadcast resumes after the last member reached.
• Plans gain sales cutoff anchors before the last start or end; the plan row's composition is saved; stale subscription anchors roll forward and proration is exact in the switch modal.

Fixes

• The bot asks for a plan's new price in the plan's own currency, keeps linked resources ticked after a save, attaches a channel shared through the request keyboard, and can enable Telegram Stars and access codes again; the project buttons stay off the project dashboard.

Under the hood

• Every module is rebuilt on one layered architecture with a request-scoped tenant context bound per entry point: billing, payments, the portal, the support inbox, subscriptions, plans and passes, notifications, analytics, webhooks, teams, settings, sign-in, access codes and coupons.
• The Telegram bot's handling is split into membership, payment and message pipelines over typed state, and every domain value crosses a boundary as a typed value.
• A quality gate runs static analysis, formatting and architecture checks on every change.

Subscriby 3.6.6

Features

• Broadcasts can target a plan; webhook payloads carry the plan id and the days until expiry; "Any Subscription Plan" wording; the sales cutoff anchor is stored per pass series.

Subscriby 3.6.5

Interface and copy

• Payment prompts and plan translations updated; the compliance page uses flag components instead of emoji.

Subscriby 3.6.4

Features

• Overlapping passes in a series are prevented; the series modal lists passes as a table; season completion and sales confirmation notices in every language; the support relay honours the member's locale.

Fixes

• Trial days are capped at 365; hero spacing and creator card positions on the home page.

Subscriby 3.6.3

Features

• Support backlog notifications for unanswered messages; overlap detection for passes; invite links filtered by pass window in the bot.

Fixes

• Tenant scoping on webhook deliveries and activity logs closed a data leak; activity log descriptions cover more subject types; hero and layout responsiveness.

Subscriby 3.6.2

Features

• Subscription management and member broadcasting over MCP.