Lemon Squeezy ↗
Developer toolsDigital product checkout with merchant-of-record services.
> $1,000,000ARR · USDhistorical milestone nine months after 2021 public launch
Researched profile Company/founder self-disclosure
EmailEngine
A self-hosted gateway that exposes mailbox access through a common REST API.
Reported revenue≈ $13,000MRR · Unspecified $Current MRR stated in the interview published January 24, 2026; measurement date unspecifiedOriginal disclosure
Business modelSelf-hosted software subscription + enterprise licenseDeveloper tools
Profile depthResearched profileProduct facts and editorial breakdown
Source checkedOct 19, 2026Observation date, not revenue cutoff
Business overview
Public positioningA self-hosted gateway that exposes mailbox access through a common REST API. Andris Reinman calls it a solo business in the January 2026 interview. This establishes the reported operating model at that time, not an independently verified current staffing count.
How it makes money
A flat annual subscription for self-hosted deployments; the current website also offers enterprise perpetual-license and procurement terms.
Business breakdown
Researched Oct 19, 2026Source-linked product facts, followed by MRRTrace analysis of the customer problem, workflow, trade-offs and questions to test.
The customer problem
Developers adding mailbox features must deal with differing providers, authentication and message synchronization. EmailEngine presents a common HTTP interface and webhooks while running on infrastructure controlled by the customer. Its documentation covers connecting accounts and integrating incoming or outgoing messages with another application, rather than replacing the customer's entire CRM or support product.
Core workflow
- Deploy the gateway and its required data store, then activate a trial or license.
- Connect authorized mailboxes and configure account authentication through the supported provider flow.
- Use API requests and webhooks in the host application, checking synchronization and error handling before wider rollout.
What customers pay for
The current annual plan covers unlimited mailboxes and instances, with infrastructure operated by the buyer. Editorial hypothesis: the buying decision should be tested against implementation and maintenance effort avoided, not mailbox count alone. A focused alternative could begin with one integration problem that repeatedly blocks a particular class of application. Validate installation success and time to a reliable workflow, then observe support tickets and renewal willingness. A large free developer audience is only a starting point; it does not reveal how many teams have the paid problem.
Distribution signals
Observed channels and entry points; their performance is not inferred.
- Related developer projects and comparison content
The founder describes referrals from his email-related projects and search comparison articles. He does not establish net customer gains from comparisons, so their effectiveness remains a qualitative account.
Evidence
Trade-offs
- Editorial risk: customer-managed infrastructure reduces hosted operating duties but produces varied environments that complicate diagnosis.
- Editorial risk: a broad mailbox abstraction must keep handling authentication changes, retries and synchronization anomalies even when the commercial package is simple.
Open questions
- Which mailbox workflow would a technical buyer pay to stop maintaining internally?
- Can a buyer install and operate the product without support costs overwhelming a fixed subscription?
Research sourcesFounder income and operating interview Official product and current terms Official annual pricing Official documentation Official source repository and license notice
A MRRTrace reading of public product material. Trade-offs and questions are editorial analysis.
Revenue evidence
Founder disclosure in interview≈ $13,000MRR · Unspecified $ · Current MRR stated in the interview published January 24, 2026; measurement date unspecified
- Reporting period
- Current MRR stated in the interview published January 24, 2026; measurement date unspecified
- Figure as of
- Not provided
- Reporting method
- Founder disclosure in interview
- Source checked
- Oct 19, 2026
- Source published
- Jan 24, 2026
The EmailEngine account reports $13k MRR; separate open-source donations are not added. Annual subscription billing does not turn the stated MRR into cash collected that month. Exact measurement day and ISO dollar currency are unstated; this remains a historical self-report.
Andris Reinman first-person interview, January 24, 2026This historical disclosure is separate from any current Stripe connection shown on this page. MRRTrace has not audited the business. Revenue is not profit, and historical figures are not current earnings guarantees.
Pricing
Pricing pageAnnual subscription: $1,450 or EUR 1,200 excluding applicable VAT; enterprise perpetual terms available
The source page may change its prices, limits, or offer after the recorded check date.
What founders can learn
Editorial notesTurn repeated protocol-integration work into a supported, self-hosted product for technical buyers.
Before you build something similar
- Customers must operate the infrastructure; self-hosting does not remove the need for support.
- Provider authentication changes and synchronization edge cases require continuing specialist maintenance.
- Source availability permits inspection but does not imply free commercial use.
These are MRRTrace observations, not statements by the founder or proof of a repeatable outcome.
Source material
5 sources- Founder income and operating interview Public source · Checked Oct 19, 2026
- Official product and current terms Public source · Checked Oct 19, 2026
- Official annual pricing Public source · Checked Oct 19, 2026
- Official documentation Public source · Checked Oct 19, 2026
- Official source repository and license notice Public source · Checked Oct 19, 2026