Two front doors,
one email platform.
sevk is an email platform with two front doors: a dashboard for marketers, founders, and AI agents, and a first-class API, SDK, and CLI for developers. Same data, same deliverability, no second-class citizens.
One system,
not two products.
Founded in Istanbul. Small team. We write our own code and ship the product we want to use.
Most email tools force a choice: a visual dashboard for non-technical users, or a raw SMTP/API service for engineers. Teams end up paying for two products and syncing them with glue code.
sevk is one system. Contacts, segments, broadcasts, and transactional sending sit behind the same database, the same API, and the same UI. Marketers do not wait on engineering. Engineers do not reimplement the dashboard.
How we decide,
what we ship.
How we decide what to build, what to charge, and what to say no to. None of these are aspirational; they are the rules we use today.
Build what we use
We use sevk to send our own transactional and marketing email. If it annoys us, we fix it.
Built for both sides
Marketers, founders, and AI agents work in the dashboard. Developers work against the API, SDK, and CLI. Neither side is an afterthought.
Honest pricing
Flat per-email pricing. No plan tiers, no feature gates, no annual contracts to unlock deliverability.
Ship, then talk
Changelog before press release. The roadmap page reflects what we are actually working on.
Remote team, a few overlapping hours a day. Most work happens in writing: pull requests, design docs, Linear tickets. Meetings are scheduled, short, and have an agenda.
Everyone ships. Designers open PRs, engineers write copy, the founder answers support tickets. Titles matter less than the next thing going out.
We are opinionated but not precious. Disagreements get resolved in a call, decisions get written down, and we move on.