Hi HN,I’m building cripta.to, a service that deploys and manages a dedicated email server inside the customer’s own cloud account.The current PoC supports Hetzner Cloud, with other providers planned. It runs Stalwart with Bulwark webmail and configures DNS, TLS, DKIM, SPF, DMARC, spam filtering, monitoring, updates and backups. Customers pay their cloud provider directly, can add their own SSH keys, and can revoke cripta.to’s management access.To be transparent, this is not currently end-to-end encrypted or zero-access. Email content is not processed by the cripta.to control plane, but cripta.to retains revocable administrative access by default to operate the service.Off-site backups are another area where I’d value feedback. The prototype currently uses S3 for testing. I’m considering customer-owned S3-compatible buckets, customer-controlled encryption keys, or making off-site backups optional. The Starter plan is €29/month plus a €99 setup fee, excluding cloud costs.I’d especially appreciate feedback on: * Whether deploying into the customer’s cloud account provides meaningful value * The revocable operator-access security model * Customer-owned versus managed off-site backups * Whether mailbox-level S/MIME encryption is worth the usability trade-offs * Pricing and the likely target customer * Deliverability or operational risks I’m overlookingOn cancellation, I’m also leaning toward handing over the working server rather than automatically deprovisioning it.If anyone is interested in trying it, comment or contact me through the site. I’ll share promo codes with HN users willing to test it and provide candid feedback.thanks!Marco