Editorial
Stalwart's code only opens. Its tests don't.
Masked email has moved from Enterprise to Stalwart's AGPL Community edition. Every open-core vendor should write down that one-way promise. But the tests that help outsiders change the code are going the other way.
Inês Valente4 min read

In v1.1.1, released on 16 November, Stalwart moved masked email out of Enterprise and into its AGPL Community edition. The 13 November announcement put the rule plainly: “Features only travel in one direction, and it is towards open source.” That is a better commitment than another open-source badge. It names which way the door can swing.
Masked email gives each website a separate receive-only address, with optional expiry, so a leaked address can be retired without changing the real inbox. Stalwart lets users create one in its account manager or applications create one over JMAP with x:MaskedEmail/set, under the urn:stalwart:jmap capability. Replies still expose the ordinary sender address. The docs describe password managers as possible integrators; I could not confirm a named integration today, including Bitwarden or Proton Pass. An API is not an integration.
Write the ratchet down
This one-way ratchet is the licence promise every open-core vendor in Europe should be asked to write down. FoxIDs went BSL and then its repository vanished; Daytona archived the AGPL repository that made it. Neither story needs another general declaration of affection for open source. What matters is whether tomorrow's users keep the rights today's users were offered, and whether the maintained code is still there to exercise them on.
Stalwart has a precedent, not just a sentence. On 31 January 2025, it moved authentication against third-party OpenID Connect providers into the open-source edition. Masked email is the second crossing. The November post also removes the 150-mailbox floor for Premium Support: every Enterprise licence now gets priority portal and email access, including sponsors' licences. There is no guaranteed response time without a separately paid SLA. Access to an engineer and a contractual deadline are different purchases.
The answer key stays inside
But the promise has an awkward neighbour. In “Private Tests, Public Code”, published on 16 October, Stalwart said its unit, integration and protocol conformance tests, stress tests and fixtures were moving to a private repository. New features would be developed privately, then published as completed single commits. The stated target is AI-assisted cloning: give a machine both the implementation and the tests, and the tests become an answer key for a rewrite that drops the original licence.
That fear makes sense. Maintaining a mail server costs money; producing a plausible imitation is getting cheaper. The post distinguishes legitimate forks from attempts to strip away licence obligations, and says it considered, then rejected, a source-available licence. Keeping release code under AGPL is a meaningful choice. Keeping tests private is another choice, not evidence of a licence breach. The contributor policy also requires a Fiduciary Contributor License Agreement, assigning copyright to a fiduciary with a reversion clause.
Still, the code is open while a major part of what lets an outsider change it safely is not. A mail server can compile and still mishandle an address that expires at the wrong moment. Without the project's regression tests, an independent maintainer must rediscover which behaviours are deliberate and which mistakes have already been caught. Single completed commits show the finished change, not the sequence of smaller decisions that led there. Neither barrier removes the right to fork. Both make using it more expensive.
The ratchet should cover tests too, or at least the tests for features that cross from paid to open. Masked email crossed; its tests stayed shut under the published policy, with no exception announced. Releasing those tests would give the recipient more than code to read. It would give them the project's own checks to run before changing what happens to somebody's mail. The AI-clone risk would remain. So would the cost of asking everyone outside the company to rebuild that confidence alone.
There is still a business to pay for
I read the pricing and compare pages today. Community is free, with unlimited mailboxes. Enterprise starts at €2.00 per mailbox per year, with a 25-mailbox minimum: €50 a year. Graduated annual rates fall to €0.89 in the 50,000–99,999 tier, not across the whole bill. Multi-tenancy, SCIM provisioning, read replicas, sharded storage, live telemetry, archiving and AI spam model tiers remain Enterprise features. There is room to charge without taking back yesterday's gift.
Stalwart Labs Ltd, registered in England and Wales, is the contracting company for UK, EU, EEA and Swiss customers; Stalwart Labs LLC in Sheridan, Wyoming, covers everyone else. The team is remote. Stalwart is not in the directory yet; its GitHub repository had 16,006 stars when checked today. Those are many potential readers of the code. Whether they can become maintainers matters more than the count.
The next Enterprise feature to cross over will be worth watching. Whether any tests follow it through the gate will be the more interesting release note.
Monday digest
Europe’s best new software, every Monday.
Top launches, new listings and stories from the Journal. One email, skipped on quiet weeks.
Every product in the directory is checked before it goes live and shows where it’s made. Explore the directory

