<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Sebastian Vargas</title>
    <description>The latest articles on Forem by Sebastian Vargas (@juansesdev).</description>
    <link>https://forem.com/juansesdev</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3913251%2Ff67a60af-3245-4eb7-9e64-6eb2b9a0e0b5.jpeg</url>
      <title>Forem: Sebastian Vargas</title>
      <link>https://forem.com/juansesdev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/juansesdev"/>
    <language>en</language>
    <item>
      <title>Tired of overpaying for emails, I built Senddock: A Self-Hostable Email API and Campaign Platform</title>
      <dc:creator>Sebastian Vargas</dc:creator>
      <pubDate>Tue, 05 May 2026 06:44:55 +0000</pubDate>
      <link>https://forem.com/juansesdev/tired-of-overpaying-for-emails-i-built-senddock-a-self-hostable-email-api-and-campaign-platform-37ph</link>
      <guid>https://forem.com/juansesdev/tired-of-overpaying-for-emails-i-built-senddock-a-self-hostable-email-api-and-campaign-platform-37ph</guid>
      <description>&lt;p&gt;Handling emails in modern applications often feels like choosing between two evils: either you pay a fortune to SaaS providers as your user base grows, or you fight with ancient SMTP servers that have terrible Developer Experience (DX).&lt;/p&gt;

&lt;p&gt;I wanted something with a modern, clean API (think Resend or Stripe), that could handle both transactional emails and marketing campaigns, but with the freedom to host it on my own infrastructure.&lt;/p&gt;

&lt;p&gt;Since I couldn't find exactly what I was looking for, I built &lt;a href="https://senddock.dev" rel="noopener noreferrer"&gt;&lt;strong&gt;Senddock&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is Senddock? 📧
&lt;/h2&gt;

&lt;p&gt;Senddock is a &lt;em&gt;developer-first&lt;/em&gt; platform and API for everything related to email. We designed it with the architecture that most devs and agencies need today in mind.&lt;/p&gt;

&lt;p&gt;These are the core pieces (you can deep dive into our &lt;a href="https://docs.senddock.dev" rel="noopener noreferrer"&gt;documentation&lt;/a&gt;):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Transactional &amp;amp; SMTP:&lt;/strong&gt; Send confirmation emails, password resets, etc., using our RESTful API or SMTP credentials.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Campaigns &amp;amp; Subscribers:&lt;/strong&gt; It's not just transactional. You can manage subscriber lists, segment audiences, and launch mass campaigns.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Workspaces &amp;amp; Projects:&lt;/strong&gt; Perfect for agencies or multi-tenant architectures. You can separate clients or dev/prod environments natively.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Templates:&lt;/strong&gt; Manage your email designs from a single place.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Analytics &amp;amp; Webhooks:&lt;/strong&gt; Track open rates, clicks, and bounces. Connect webhooks so your backend can react when a user clicks on an email.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Developer Experience (DX) 💻
&lt;/h2&gt;

&lt;p&gt;We wanted the integration to be as frictionless as possible. Here is what a basic send looks like using our API:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Example using Fetch (or your favorite HTTP client)&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;API_URL&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;https://api.senddock.dev/v1/send&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;response&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;API_URL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="na"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;POST&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Authorization&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Bearer YOUR_API_KEY&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Content-Type&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;application/json&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;
  &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="na"&gt;body&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="na"&gt;workspaceId&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;ws_12345&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;projectId&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;proj_67890&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;to&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;user@example.com&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;subject&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Welcome to our app!&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;templateId&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;tpl_welcome_01&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;data&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Dev.to User&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;})&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;data&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
&lt;span class="nx"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Message ID:&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;messageId&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  The best part: It's Self-Hostable 🛠️
&lt;/h2&gt;

&lt;p&gt;For me, this is the killer feature. If you don't want to rely on our cloud, you have total control over your data and privacy.&lt;/p&gt;

&lt;p&gt;You can spin up the entire Senddock infrastructure on your own server. We've documented the whole process, from &lt;a href="https://docs.senddock.dev/guide/environment" rel="noopener noreferrer"&gt;environment requirements&lt;/a&gt; to &lt;a href="https://docs.senddock.dev/self-hosting/installation" rel="noopener noreferrer"&gt;installation and configuration&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  I'd love to hear your feedback 🤝
&lt;/h2&gt;

&lt;p&gt;Senddock is fresh out of the oven and the documentation is live at &lt;a href="https://docs.senddock.dev/" rel="noopener noreferrer"&gt;docs.senddock.dev&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you are building a SaaS, running an agency, or just like to tinker with infrastructure tools, I invite you to check it out.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;What features do you consider vital in an email service that are usually missing?&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;If you self-host, what are the common hurdles you find when setting up these kinds of platforms?&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'll be reading and replying to all comments below! 👇&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>marketing</category>
      <category>docker</category>
      <category>selfhosted</category>
    </item>
  </channel>
</rss>
