Changelog

You can now see who opened your emails and which links they clicked. Turn on tracking from the Emails page in the dashboard (opens and clicks are separate switches), and every new send records its engagement: counts in the email log, a per-event timeline on each email, and email.opened / email.clicked webhook events for your own systems. Any single send can override the project setting with the new tracking field on the send API.

Tracking links live on our tracking host by default, but you can put them on your own domain instead. On the Domains page, enable branded tracking links, add the one CNAME record we show you, and we handle the certificate automatically. Until the record is live your emails simply keep using the shared host, so nothing ever breaks.

Tracking is off by default and never applies retroactively: only emails sent after you switch it on are measured.

Running out of included emails mid-campaign used to mean a hard stop until the next month. With Always On, your emails keep sending past your plan’s included volume, and the extra usage simply goes onto a monthly invoice at your plan’s overage rate (the pay-as-you-go rate on the Free plan).

Paid plans have Always On active out of the box. On the Free plan it is an opt-in toggle on the Billing page, with a safety cap on how much extra usage can accrue in a period so there are never surprise bills. You will get an email the moment overage starts, a live running total in your dashboard, and the invoice when the period ends.

Settling an invoice is automatic where possible: we collect from your wallet balance or saved card first, and otherwise send you a secure Paystack payment link, with a Pay now button in the dashboard too. Keep one invoice at most outstanding and nothing ever interrupts your sending.

Freelancers and agencies can now earn recurring income with SendByte, in three ways. Refer clients with a link and earn a share of what they spend. Manage email for clients from your own workspace while they keep their own account. Or resell SendByte at wholesale and set your own price.

One dashboard, one partner per account, and monthly payouts in Naira. See how the models compare and choose the one that fits on the partners page, or email partners@sendbyte.africa.

When an address hard bounces or marks a message as spam, we suppress it so you keep a healthy sending reputation. Sometimes that address is fixed and the person genuinely wants your email again. You can now request removal directly from the dashboard.

Open the new Suppressions page, find the address, and send a confirmation email. The recipient clicks a link to confirm they want your mail, and only then is the suppression removed automatically. Because the recipient has to opt back in themselves, you stay compliant and your reputation stays protected. The whole flow is also available through the API and the Node SDK, with webhook events for each step so you can track it in your own systems.

Getting DNS records right is the hardest step of setting up a sending domain, and when it goes wrong it usually fails silently: the records look fine to you, but verification never completes.

If your domain has been sitting unverified for a couple of days, we now send you a short note walking through the most common causes, things like propagation delays, a host field that doubles up your domain, or proxied records on Cloudflare. Still stuck a week later? We offer to check your DNS for you. Just reply to the email, tell us where your DNS is hosted, and a person will look at what is publicly visible and tell you exactly what to change. Once your domain verifies, the check-ins stop on their own.

Our private beta has ended and SendByte is open to everyone. You can create an account and send your first email in minutes, no invite needed.

Every new account starts on the Free plan with 3,000 emails a month and no card required, plus a one-time welcome credit so you have room to grow past the free quota from day one. When you are ready for more, Startup and Scale are a click away.

Thank you to every beta developer who sent with us early and shaped the product. This is just the start.

You can now reference a template in your POST /v1/emails call by either its ID or its name, so you can use the friendly name you gave it instead of looking up a UUID. The template editor now shows a copyable Template ID right above the editor, and the API docs use the correct ID format. Sends that reference a template that does not exist now return a clear, actionable error.

We refreshed the icons throughout the dashboard to a single, modern, consistent set. Nothing moved and nothing changed in how things work. The icons are just clearer and easier to scan, and they stay crisp in both light and dark mode.

You can now raise a support ticket without leaving the dashboard. A new Support page lets you send us a question or report a problem, pick a category so it reaches the right place, and see all of your past tickets and their status in one list. We reply by email, so the whole conversation lands in your inbox.

Not signed in, or just want to talk to us before you start? There is now a Contact page on the website where anyone can send a message. Both routes go to the same team, and you get a ticket number on the spot so you know it reached us.

We also fixed a small thing on the email log: the Refresh button now shows a clear “Refreshing” state when you tap it, so it is obvious it is pulling the latest sends.

The dashboard sidebar has been refreshed. Every item now has an icon and a clearer label, the sections are easier to scan, and the page you are on is marked more clearly. “Emails” is now “Email log”, since that is what the page is: a record of every send and its status. The navigation also works better with a keyboard and with screen readers.

Billing now has its own page. Your plan, renewal date, pay-as-you-go wallet, top-ups, and payment history all live together in one place, with the full plan comparison alongside. The Usage page stays focused on how much you are sending and your delivery over the last 30 days, and links across to Billing when you want to change plans.

You can now manage your account from inside the dashboard. A new Account page lets you update your name and change your password without leaving the app, and the sidebar now shows which account you are signed in as. Changing your password signs you out on your other devices and keeps you signed in where you are.

You can now connect SendByte to AI assistants and coding tools through the new SendByte MCP server. Install it with npx @sendbyte/mcp, point your client at it with your API key, and your assistant can send email, check sending domains, render templates, and run a pre-send spam-risk check, all through your own account. It works with Claude Desktop, Claude Code, Cursor, and Continue. See the MCP server guide in the docs to set it up.

The Usage page now shows every plan side by side, with your current plan clearly marked, so you can compare and switch in one place instead of guessing what each tier includes.

API keys are easier to tell apart. Each key now shows its last four characters and the date it was created, and you can rename a key at any time. Keys are still hashed and shown only once, so a lost key means creating a new one, but now you can identify the keys you already have at a glance.

Domain setup reads more clearly too. Each DNS record now shows a simple Found or Missing state, with required and recommended records labelled separately, so it is obvious what still needs publishing.

We redesigned sendbyte.africa from the homepage out. Every page is easier to scan, with a clearer story of what SendByte does and who it is for, and the same fast, lightweight pages on any connection.

Pricing is clearer too. The pricing page now lists every add-on with its fixed Naira price, alongside a short section answering the common billing questions: how overage works, how we hold your price steady when the exchange rate moves, and what the free tier includes. Pay-as-you-go is ₦300 per 1,000 emails.

We also rebuilt the provider comparison pages into a side-by-side view that shows, honestly, where SendByte fits and where the other provider is the stronger pick. The SDK section now lists all four official SDKs, Node.js, Python, PHP, and Go, each with a one-line install command.

Choosing an email provider should not mean trawling ten tabs of pricing pages billed in the wrong currency. We added side-by-side comparisons of SendByte against SendGrid, Resend, Postmark, Mailgun, ZeptoMail, Amazon SES, and MailChannels, each one honest about where the other provider is the stronger pick. They tie straight into the cost calculator so you can see the all-in Naira cost for your own volume.

We also published a set of developer guides: how to send transactional email in Nigeria, a practical SPF, DKIM, and DMARC setup, why mail lands in spam and how to fix it from Nigeria, what dollar-billed email really costs, moving off MailChannels cleanly, and sending receipts and OTPs with Paystack and Flutterwave webhooks.

You will find the comparisons under Compare and the guides on the blog.

The dashboard now has a dark mode. Choose light, dark, or follow your system from the switch in the sidebar, and your choice sticks across visits. Every screen is covered, from the overview and email logs to domains, keys, and the template editor, with contrast tuned so everything stays easy to read.

The dashboard is also built for small screens now. The sidebar folds into a menu you can open with one tap, long tables scroll cleanly instead of getting cut off, and forms and dialogs fit comfortably on a phone. You can check sends, add a domain, or rotate a key from anywhere.

We also added a Docs link inside the dashboard, so you can jump straight to the documentation without signing out.

Adding a sending domain is easier to follow. The dashboard now leads with the one record that is required to verify (DKIM), and labels SPF and DMARC as recommended rather than optional, with a clearer note on what each one does for your inbox placement. Nothing changed about how verification works, just how clearly it reads.

The docs home page is now code-first too. It opens with the install command and a copy-paste snippet to send your first email, so you go from landing on the docs to a working send in seconds instead of hunting for the example.

We cut the Startup plan to ₦2,000 per month for 6,000 emails. It is built for founders shipping their first product: your own sending domains, team members, templates, and email support, at a price you barely feel.

Pay-as-you-go also drops to ₦300 per 1,000 emails, with a minimum top-up of ₦1,000 and a balance that never expires.

Every paid plan, Startup included, sends with no SendByte footer on your emails. Prices stay fixed in Naira and billed through Paystack, so a moving exchange rate stays our problem and not yours.

A broad reliability and security pass landed across the platform:

• Scheduled sends now respect scheduled_at and go out at the time you set, not immediately.
• Attachments and Bcc recipients are delivered correctly on every send.
• The API and dashboard now ship modern security headers, and dashboard sign-in uses httpOnly session cookies.
• The official SDKs retry safely on rate limits and transient errors and attach an idempotency key automatically, so a retried send is never delivered twice.
• Sending is rate-aware end to end, so bursts no longer risk throttling or delays.

Early access to SendByte is here. If you joined the waitlist, your invitation to set up your account is on its way. Waitlist members start on our Scale plan, free for the first 3 months, then 50% off after that. Check your inbox for your setup link, or just reply if you need a hand.

The waitlist is now full, so public signups are paused until we go live.

Every password field in the dashboard now has a show/hide toggle, so you can check what you typed before submitting. It is on sign in, sign up, password reset, and the connect screen where you paste an API key.

You can now send through SendByte over SMTP, not just the REST API. Point any app or framework that has SMTP settings at smtp.sendbyte.africa on port 587, 465, or 2525, use apikey as the username, and your SendByte API key as the password. That is the whole migration: change the host and credentials, no code change.

SMTP sends run through the same pipeline as the API, so you keep verified-domain enforcement, suppression, abuse protection, the email log, and webhooks. Use a test key to develop in sandbox, a live key to send for real. See the SMTP guide in the docs to get connected.