The only possibility left is "dedicated storage". That works for static ressources. But the `page` content itself is dynamic and changes often, so you will need more than "bring your own S3" and something like "bring your rds" but that starts to be pretty complicated. Quip though still offer on prem AFAIK.
At the end of the day, the issue with collaborative tools, is that you can't e2e encrypt easily, and almost impossible if you offer full text search. The best solution is to trust your provider for data security. And use maybe some daily backups in your own network.
What's going to end up happening if more vendors decide you can only use their service from their cloud is the largest enterprises and governments are going to exclusively use Microsoft and AWS since they're more than willing to just build you your own cloud that meets whatever security and disconnection requirements you have, no matter how stringent. Already no new government projects that still have a choice are going with Atlassian tooling.
We'll see how it goes for them, I guess. Maybe they don't need governments and Fortune 500s and can get by selling exclusively to startups with no real security or lock-in avoidance requirements.
The idea of using their cloud service (Atlassians) wouldn't be that daunting if it wasn't for the consistent feed back I see here and else where that performantly, it absolutely sucks.
Time would be better spent contributing to an open source alternative like Athens!
Are you suggesting privacy and data ownership concerns are only limited to enterprises?
These factors make sense to me. Note that Gitlab believes the opposite so on prem is also free.
It would be nice if AWS could deliver a smooth OAuth experience so that in a few clicks, a user could provision an S3 bucket and share it with a service provider as easily as they can grant access to a GitHub repository.
Sounds like an opportunity ;)
Starting or rearchitecting a project gives you the rare chance to make decisions that your competitors never even had available to them. You can leverage new tech to move faster, and you can learn from their mistakes to avoid their most costly traps.
“Bring your own S3 bucket” actually sounds pretty awesome and I wish more companies would do this. Everybody wants to be a middleman controlling the transaction, but they’re missing a whole class of customers by not offering self-directed storage options.
This is a great example of a decision Notion could make now, that Asana would have a hard time adapting to. As long as they’re rearchitecting, they should keep an eye out for opportunities like that.
As for how much I’d pay – if I’m the only party with access to my raw data, and I can run the software locally even if Notion goes out of business – for a team of 5-10, I would pay $50-75 per user per month.
Open source Notion clone that you can host locally.
Curious what you'd be willing to pay for this, as it's exclusively an enterprise feature. My guess is an absolute minimum of $50k/year contract value, or 250-350 users at an enterprise per-seat price (just guessing).
Aside from going fully on prem, the idea of strictly dedicated storage is interesting -- like "bring your own S3 bucket" simplicity. I don't see that often outside of $10 desktop apps.