How Should We Calculate Expected DID Space Costs for Customers?
Hey team, quick question on DID Space pricing.
As we get deeper into DeBOS (Sovereign Cloud Software), one thing we want to communicate clearly to end-users is what they can expect to pay for their DID Space. Since DeBOS does not charge per user or per seat, the DID Space bill becomes the only variable cost tied to their operational footprint. For transparency and forecasting, we need a reliable method to estimate:
- how storage usage is calculated,
- how pricing scales across tiers, and
- what the predictable monthly cost looks like for a typical business.
What’s the best way for us to programmatically determine (or approximate) how much a customer will pay based on their DID Space usage? Is there an API endpoint, pricing formula, or recommended estimation method that we should be using?
Our goal is to give DeBOS users a simple forecast like: “Based on your expected data footprint, here’s what your DID Space will likely cost each month.”
Anything you can share on how to model this accurately would be extremely helpful.
Thanks!
and also Looks like this page may need a translation Storage of personal data
5 条回复
你好,你能说明一下什么是 DeBOS 吗?你们又是怎么去使用 DID Spaces 为用户提供服务的,怎么跟 DeBOS 结合的? 你们使用了哪个组件?
因为官方已经提供了可用的 DID Spaces https://www.didspaces.com/ ,可以直接无缝连接。
DeBOS stands for Decentralized Business Operating System — a Sovereign Cloud Software (ScS) approach where each business runs on:
We don’t store any customer data. Everything created in DeBOS lives directly inside the company’s own DID Space, and DIDSpaces.com handles all storage and billing.
What companies actually store (realistic footprint)
Most business data is extremely lightweight:
The only data that grows meaningfully is uploaded files, such as:
Even with regular uploads, most small to mid-sized businesses end up around:
5–20 GB of total storage in their DID Space.
This gives them plenty of room for structured data + attachments without hitting large-scale storage levels.
DID Spaces tracks usage and billing directly — DeBOS simply writes into the user’s own Space.
How DeBOS ties ArcBlock’s tools together
DeBOS isn’t replacing ArcBlock’s components. It serves as the business layer that connects them into a single workflow.
Here’s a clean example.
Example: A company using only two components — DeBOS + Payment Kit
Key takeaway:
Businesses can choose how much of ArcBlock’s suite to use.
Some will only use:
Others may add:
But DeBOS is the layer that pulls everything together into a unified business system, while DID Spaces remains the single source of truth for data.
看下来,did spaces 最后有一个接口告诉你们预计花费的金额是多少,这个我会考虑在最近支持一下。在此之前你其实也可以自己预估用户的成本:
(x-space-used-unit - 10) * 0.01 ABT,注意这里面的 10 是免费赠送的额度, 0.01 ABT 是官方对每个单元用量的定价。
Thanks, this explanation helps a lot. Using the HEAD request to read the
x-space-used-unitvalue gives us exactly what we need for transparency inside DeBOS.I do have a question as we think through onboarding real businesses. Right now a user can launch a blocklet on ArcBlock Cloud using a credit card, which is very straightforward. But if that same user later exceeds the 10 free units in their DID Space, how do they pay for the additional usage? Is that currently ABT-only, or is there a path for non-crypto users to handle DID Space billing in fiat the same way they pay for hosting?
Most traditional businesses won’t feel comfortable acquiring and maintaining ABT just to cover small amounts of storage usage, even though the cost itself is very low. Understanding how you see this evolving will help us plan a smoother onboarding flow and set expectations correctly. Happy to keep discussing this as we go.
支付方式上,我们目前还支持 USD,了解更多支付方式可以参考: https://www.arcblock.io/docs/arcblock-payment-kit/en/add-payment-mothods