4 ms·

>my stack is, maybe, a little boring. >Dedicated AMD 32 core RAID 10 servers from Hetzner running LXD for customer containers — seven containers per server on

>my stack is, maybe, a little boring. >Dedicated AMD 32 core RAID 10 servers from Hetzner running LXD for customer containers — seven containers per server on the cheapest plan. Each dedicated server has their filesystem encrypted with LUKS — including /boot >All servers run a slightly modified version of Ubuntu, resolve DNS queries using one of my 8 DNSCrypt servers, are managed using on-premise Canonical Landscape and connect to a Hashicorp Vault instance for credentials and whatnot. >Backups are handled by another big Hetzner server — sitting at 60 TB of storage right now ... I'd love to see what you consider exciting! Just a side note, do you all have revenue? This seems very overbuilt for a private beta product.

jamesponddotco 7y ago
> ... I'd love to see what you consider exciting! I mean, in the age of Kubernetes and AWS, having your entire stack running on a single server does sound kinda dull to most people. I rather have the performance and simplicity, though. > Just a side note, do you all have revenue? This seems very overbuilt for a private beta product. Yes. All customers on the private beta have a 50% discount, but our profit margin is pretty high, to be honest. The "Medium" plan, which is where all tests are happening, cost us €215,88 per month, which includes the dedicated server, one IP address for each LXD container, about 700 GB of bandwidth from BunnyCDN and emails by Mailgun. In that plan, we offer 16 GB of ECC memory and 240 GB of NVMe storage. One of our competitors charge $1500 per month for 200 GB of storage, our price is €599.00 per month. So even with high-profit margins, our cost is below our competition. Which makes you wonder how much profit they make. But, of course, none of this account for operational costs, employee costs, SaaS costs and things like premium plugins which are offered by default and CDN bandwidth above 700GB — which realistically speaking, will be higher for some customers.
- eb0la 7y ago
  Kubernetes and wordpress is not that simple. Might be sexy, but not simple. For me, the stopper is WP is thought to be used inside a server with _mutable_ access to everything; whilst k8s needs containers. This looks good for day-to-day use until you realize your wp needs updating and needs to be done by the operator/editor and somehow propagated back to the system that builds the container. Usually this is an air gap.
  - jamesponddotco 7y ago
    I dislike Kubernetes in general, and much prefer something like LXD for WordPress. My point was that most people consider my way of doing things "boring", while everything else, i.e., serverless technology, is over hyped.

jamesponddotco 7y ago

> ... I'd love to see what you consider exciting! I mean, in the age of Kubernetes and AWS, having your entire stack running on a single server does sound kinda dull to most people. I rather have the performance and simplicity, though. > Just a side note, do you all have revenue? This seems very overbuilt for a private beta product. Yes. All customers on the private beta have a 50% discount, but our profit margin is pretty high, to be honest. The "Medium" plan, which is where all tests are happening, cost us €215,88 per month, which includes the dedicated server, one IP address for each LXD container, about 700 GB of bandwidth from BunnyCDN and emails by Mailgun. In that plan, we offer 16 GB of ECC memory and 240 GB of NVMe storage. One of our competitors charge $1500 per month for 200 GB of storage, our price is €599.00 per month. So even with high-profit margins, our cost is below our competition. Which makes you wonder how much profit they make. But, of course, none of this account for operational costs, employee costs, SaaS costs and things like premium plugins which are offered by default and CDN bandwidth above 700GB — which realistically speaking, will be higher for some customers.

eb0la 7y ago
Kubernetes and wordpress is not that simple. Might be sexy, but not simple. For me, the stopper is WP is thought to be used inside a server with _mutable_ access to everything; whilst k8s needs containers. This looks good for day-to-day use until you realize your wp needs updating and needs to be done by the operator/editor and somehow propagated back to the system that builds the container. Usually this is an air gap.
- jamesponddotco 7y ago
  I dislike Kubernetes in general, and much prefer something like LXD for WordPress. My point was that most people consider my way of doing things "boring", while everything else, i.e., serverless technology, is over hyped.