Jeff, Burke, All,
Lance Johnson here - partner with Tim Urban at Patmos who chimed in earlier. I figured I'd try to address a few things about Patmos since there are some specific questions.
First, Burke is right that our current website lacks a lot of functionality. While the company is officially a year old, we've been in a quiet launch phase and have been focused on ensuring that our infrastructure is working correctly while focusing on our earliest customers. We are actively working on building out our public-facing website, but we have a fully functional cloud infrastructure up and running. Within the next 1-4 months the ability of customers to self-onboard will be in place. In the meantime, all onboarding is being done on a personalized basis, and we're always open to talking to anyone that is interested in what we are doing.
To address Jeff's specific questions:
Is your server hardware self-hosted? Colocated? We own all of our own hardware, including all of the racks, routers, switches, and server metal. We are currently operating out of a private data center in Kansas City, but we are in a specifically demised, privately caged space. Our long term plan is to own at least one of our own entire data centers, but as I'm sure many people here are aware, that is highly capital intensive, so that is something we are working toward. Like many other smaller players in the market, we are open to colocation for future expansion, but it is by no means our sole model.
What kind of peering do you have? We currently use a four-carrier blend for IP transit, but we also have access to a large peering network through our data center. Some of our peering networks include KCIX, AMS-IX Bay Area, MICE, FCIX, STLIX, HOUIX, DE-CIX NY, IX-Denver, SIX Seattle, and DE-CIX Frankfurt.
I think those are important questions considering most hosting providers just bootstrap things off AWS, Google Cloud, or elsewhere. We are definitely not just bootstrapping off of other providers. That said, we do have one customer in production that has need of a wider CDN than we can directly support with our own hardware at this time, so we have worked with another provider in that specific case to add some geographically distributed nodes for the time being. Even in the case of this specific customer, all of their logic is running on our hardware, we leverage those edge nodes exclusively for content delivery.
And also some of Burke's specific points:
The hosting offers S3 storage - that is AWS. To be clear our object storage solution is fully in-house, it is not AWS. S3 was developed by Amazon, true, but there are many S3-compatible solutions that are not riding on AWS. All objects stored in our solution are stored in our own data centers.
Patmos.Tech sits on Cloudflare. We do use Cloudflare for DNS. We know that the type of service we are offering is basically painting a target on our back. Cloudflare does what it does very well, and they have also taken strong stands on freedom of speech on the internet. Given this, we feel confident that Cloudflare can serve us well at this time. Cloudflare is not our "host." I agree, that would raise some red flags.
Their MX records are pointed to Google. Absolutely right. We played with other options, including ProtonMail, which we used for almost a year, but building out a scalable business on ProtonMail and Calendar proved to be nearly impossible. What we found is that most business is not conducted by email, and when email is involved, 80% of the time someone using Google is involved, so those conversations enter the Google ecosystem anyhow. Even just look at where this Group conversation is taking place. We don't want to pretend that we can hide from Google. While we don't see Google as a long-term provider, like Cloudflare, they are good at what they do, and we want to focus on making our core product offering great, not trying to hide from big brother.
If anyone is interested in talking about what we do, we're always here to talk. And we're always open to hearing constructive comments about what we can do to better serve our customers and communities.
Pax,
Lance