TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Is bring your own cloud considered self-hosting?

2 点作者 Ryner001大约 1 年前
Hello,<p>We are creating a b2b SaaS app that will need access to your codebase. As you might imagine not all companies are happy with sharing their codebases with third parties.<p>I was researching self-hosting options but honestly, all of them seem kind of complicated. So decided to borrow the wisdom of the HN crowd.<p>Here are a few options I came up with:<p>1) Use docker-compose -&gt; This is probably a no-go. We are e2e testing app running headless Chrome with codebase access. So you would need to give us quite a huge VM.<p>2) Packaged Kubernetes - This could work but we would need to run everything including the database inside the k8 cluster. And figure out a way to somehow package it including all of the operators etc<p>3) Bring your own cloud - For a small startup like ours (3 people) this seems like the most realistic option. You will give us a GCP project and we will point our terraform there. In a few minutes, you should have your deployment ready.<p>I should also mention that I know for HIPAA and very security-conscious companies cloud approach is a no-go. But we would first target smaller startups (20-100 engineers).<p>For those who work in such environments would you be ok with that?<p>Bonus question: Or would you share your codebase with a SaaS app that has SOC2 type II compliance?

1 comment

kgdiem大约 1 年前
If a customer has such stringent requirements, can’t you offer 2 &amp; 3 then use the contract approval &#x2F; signing period to get ready? Potentially even having the customer fund #2?<p>If you already have terraform it should be low-ish effort to do #3 as it is.
评论 #39480504 未加载