Cerberus: Three Responsive HTML Email Templates You Copy Into Your Own Build
Simple, but solid patterns for responsive HTML email templates and newsletters. Even in Outlook and Gmail.
At a glance
- What is it?
- Cerberus is a set of three annotated HTML email templates, fluid, responsive and hybrid, maintained under the MIT licence. It ships no build step, no components and no CSS framework, which is exactly why it stays portable across Outlook and Gmail.
- Who is it for?
- Adopt Cerberus if you write email HTML by hand or maintain a small in-house template and want patterns you can read line by line. Do not adopt it if you need a component library, a build pipeline or server-side rendering; it is three files, not a framework.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 62 days ago.
- What is it written in?
- Mainly HTML, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- emailmonday/Cerberus5,147 ★ · +11
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| emailmonday/Cerberus | 5.1k | 5.1k |
11 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What Cerberus Solves, and Who It Is Written For
HTML email is a rendering problem before it is a design problem. The README opens by saying that coding regular emails is hard enough on its own, and that making them responsive and accessible should not add to the headache. Cerberus answers that with a small number of patterns rather than a framework. The README describes the project as "just a few responsive email patterns that go a long way," with code blocks compartmentalized so they can be used, combined and nested to build an email.
The audience is narrow and worth stating plainly. This is for someone who writes email markup directly, or who maintains a transactional template that a backend service renders into a string. It is not for a marketing team looking for a drag-and-drop editor, and it is not a component library you import. The repository holds three top-level HTML files and a docs folder. That is the whole product surface.
A second audience is the person who inherits an email template and has to fix it. Because each template is annotated, the file itself acts as the documentation. If you have ever debugged a table layout at 2am, the value of a commented reference file is obvious.
Fluid, Responsive and Hybrid: How the Three Templates Differ
The README draws the distinction between the three files, and the distinction is about how much you rely on media queries.
cerberus-fluid.html is described as good for simple layouts such as transactional and single column emails. Fluid layouts do not need breakpoints to reflow, so this is the safest starting point when your content is a heading, a paragraph and a button.
cerberus-responsive.html is for "more complicated, shape-shifting email layouts that work on some mobile clients." That qualifier matters. The README does not claim universal support for this file. A responsive template depends on the client honouring media queries, and some clients do not.
cerberus-hybrid.html uses a hybrid approach to reconfigure the layout for different screen sizes "for email clients regardless of media query support." This is the one to reach for when you cannot predict the client. If your layout is genuinely simple, choosing hybrid buys you complexity you do not need.
The repository also carries an archived-versions folder, which suggests older iterations are kept around rather than deleted. The README does not explain what lives there or when to use it.
Getting the Files and Building a First Email
There is no installer. The README points to https://www.cerberusemail.com/ to learn more and see examples, and the repository contains the templates themselves. The practical route is to clone the repository and copy the file you want into your project.
git clone https://github.com/emailmonday/Cerberus.gitAfter cloning, the top-level entries include cerberus-fluid.html, cerberus-hybrid.html and cerberus-responsive.html. Pick one as your starting point. For a password reset or a receipt, the fluid file is the match the README describes.
The package.json declares the package name as cerberus-email, but the README documents no npm install step and no build command. Treat the package metadata as identification rather than a distribution channel.
Once you have the file, the workflow is editing HTML directly. The README states the code blocks are meant to be used, combined and nested, so the normal move is to keep the outer table structure and replace the content rows. The README does not publish a sample content row, so the markup you insert comes from your own template, not from Cerberus.
Before sending anything, open the edited file in a browser and then in the clients you care about. The README makes support claims per template; it does not provide a testing tool, and the repository has no test directory.
Where Cerberus Stops Being the Right Tool
The honest limitation is that Cerberus is a set of files, not a system. There is no templating language, no variable substitution and no partials mechanism beyond copying blocks between files. If you send twelve different emails, you own twelve copies of the same outer table, and a change to the wrapper means editing twelve files. Teams that need shared components usually reach for a build step or a template engine, and Cerberus does not provide either.
The second limitation is support scope. The README itself qualifies the responsive template as working on "some" mobile clients. That is an admission, not a marketing line. If your audience skews toward a client with weak media query support, the responsive file is the wrong choice and the hybrid file is the one the README positions for that case.
Third, the project is small by design and the release history is thin. The most recent release listed is 3.4.1 from 2022-03-19, described as an Outlook border issue fix, following 3.4 in February 2022 with dark mode and an updated documentation site. The last push to the repository was on 2026-09-14, so work continues, but the versioned releases are years apart. If you need a vendor with a support contract or a changelog you can plan around, this is not that.
Finally, package.json declares version 3.3.0 while the release list goes to 3.4.1. Do not read the metadata file as the current version.
How Cerberus Compares With MJML and Foundation for Emails
The obvious alternative is MJML, which takes a custom markup language and compiles it to table-based HTML. The difference in approach is fundamental. MJML owns the markup and generates the output; you write mj-section and mj-column, and a Node build step produces the email. Cerberus owns nothing. You write the table HTML yourself, using its files as a reference, and there is no compile step to run, no dependency to update and no generated output to inspect when something renders oddly.
That trade cuts both ways. MJML gives you reusable components, which solves the twelve-copies problem Cerberus leaves open. Cerberus gives you a file you can open, read and ship without a toolchain, which matters when the person sending the email is not the person who set up the build.
Foundation for Emails sits closer to MJML in that it is a framework with its own grid and components, and it also expects a build. If you are choosing today: pick Cerberus when the email is simple and the team is small; pick a compiler when you have many templates and want them generated from shared parts. The README makes no comparison to either, so this is a structural observation about what each tool asks you to maintain, not a claim about output quality.
Licence, Maintenance and the Cost of Upgrading
Cerberus is MIT licensed, copyright Jordie van Rijn, and the README states the intent plainly: "Let's go with something simple and permissive, shall we?" The licence text permits use, copy, modification, merging, publishing, distribution, sublicensing and sale, provided the copyright notice and permission notice are included. It ships with no warranty. In practice that means you can drop these templates into a commercial product without asking anyone. It also means you carry the notice. None of this is legal advice; read the LICENSE file in the repository before you rely on it.
The upgrade cost is the part people underestimate. Because there is no package manager flow and no build, upgrading is a manual diff. You compare your edited template against the new release and reapply your content. The release history shows why this is manageable: 3.4.1 addressed an Outlook border issue, and 3.4 added dark mode and updated the documentation site. Those are narrow, targeted changes rather than a rewrite, so a diff is realistic. It is still work you do by hand.
If you have heavily restructured the outer tables, that diff gets expensive fast. The mitigation is to keep your customizations inside the content rows and leave the wrapper markup as close to the original as possible, so a future release can be merged rather than manually reconciled.
Editorial conclusion
Adopt Cerberus if you write email HTML by hand or maintain a small in-house template and want patterns you can read line by line. Do not adopt it if you need a component library, a build pipeline or server-side rendering; it is three files, not a framework. Before committing, open cerberus-hybrid.html in the clients your list actually uses, since the README states the hybrid approach is the one that reconfigures regardless of media query support, and confirm the version string in package.json, which reads 3.3.0 while releases have moved past it.
Frequently asked questions
How do I install Cerberus?
There is no install step. Clone the repository and copy cerberus-fluid.html, cerberus-responsive.html or cerberus-hybrid.html into your project, then edit the HTML directly. The README points to cerberusemail.com for examples rather than documenting a package install.
How do I use Cerberus in an email?
Pick the template that matches your layout, then use, combine and nest the annotated code blocks to build the email. The README describes the blocks as compartmentalized for exactly that purpose.
Which Cerberus template should I start with?
The README says cerberus-fluid.html suits simple layouts such as transactional and single column emails, cerberus-responsive.html suits more complicated shape-shifting layouts that work on some mobile clients, and cerberus-hybrid.html reconfigures the layout regardless of media query support.
Is Cerberus still maintained?
The repository is not archived and the last push was on 2026-09-14. The most recent release listed is 3.4.1 from 2022-03-19, so versioned releases are infrequent even though the repository continues to receive commits.
What licence does Cerberus use?
MIT, copyright Jordie van Rijn. The README permits use, copy, modification, merging, publishing, distribution, sublicensing and sale as long as the copyright and permission notice are included, and it ships without warranty.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/emailmonday-cerberus)Star history chart for your README
[](https://hysenlabs.com/projects/emailmonday-cerberus)Was this useful?