A lighthouse does not shout.
Pharos is named after the lighthouse at Alexandria, which guided ships into harbour for roughly fifteen hundred years by doing one thing reliably and never asking for attention. That is the standard we are aiming at, and it is a high one.
Why Pharos exists
The email API market splits into two halves, and neither one is whole.
One half sells developer experience. Beautiful documentation, a clean API, an onboarding you can finish before your coffee cools. Deliverability there is an assumption — something that either happens to you or does not, with no visibility either way and nobody to call when Gmail stops accepting your mail.
The other half sells deliverability, and has done for fifteen years. It works. It also looks and feels like it was designed in 2011, and the API tells you so within about four minutes.
Pharos exists in the gap: an API a developer is glad to use, sitting on infrastructure where authentication is enforced rather than suggested and reverse DNS is checked every day rather than once. Neither half is the interesting part. The combination is.
What we believe
-
01 Proof beats promises
Every technical claim we publish should be checkable from a terminal by someone who does not trust us. Where we cannot prove something, we say so rather than phrasing it carefully.
-
02 Deliverability is a feature, not a tier
The free account sends through the same infrastructure, with the same authentication and the same monitoring, as the largest one. Charging for the thing that makes email work is charging for the product.
-
03 Documentation is product
An undocumented behaviour is a bug someone else will discover in production. Errors name the field, the docs list every status code, and the limits are published rather than discovered.
-
04 Say the limits out loud
Nobody can guarantee inbox placement, and a provider who offers you a number is selling one they do not control. We would rather lose a sale to honesty than win one we cannot deliver on.
-
05 Build for ten years
Email infrastructure is a long game and switching costs are real. Decisions here are made for the version of this company that exists in a decade, not for a quarter.
-
06 Price on one axis
You should be able to work out what Pharos costs you in ten seconds. Volume is the only variable, every plan carries every feature, and there is no negotiation to unlock a better rate.
How we work
Small and independent
No outside investment, so no pressure to grow at a speed that would break the thing being sold.
Engineers answer support
There is no tier-one script. The person reading your bounce log can also read the mail server’s response.
Quiet in incidents
When something breaks we say what happened, what we did and what changes. No status-page euphemism.
Transactional first
We would rather be the best option for mail people are waiting on than an average option for everything.
You will not find faces or founder stories on this page. That is deliberate. A lighthouse is judged by whether ships arrive, not by who is in the lamp room — and everything we would put on a team page, you can verify instead by checking our records from a terminal.