Committed capacity
Commit to capacity in an annual contract, from 1 PB. Below 1 PB but above the account quota, capacity is allocated through sales.
T4 Enterprise
For data, AI, media and institutional teams storing data at scale. From 1 PB: an annual contract with a special price from sales. We are plain about what is available and what is still planned.
Commit to capacity in an annual contract, from 1 PB. Below 1 PB but above the account quota, capacity is allocated through sales.
Set for your volume and term, not the self-serve list rate.
A Rupiah contract with PPN invoices. Payment terms are agreed with our sales team.
Stored in Dalang Data Center Pandeglang, Banten (API region id-jkt-1). A fit for data-location needs; confirm your regulatory requirements with legal counsel.
Standard S3 API. Leaving T4 carries no T4 egress fee.
A sizing workshop, then a limited trial with your own data before you commit.
Enterprise buyers deserve this before the first meeting. The status column mirrors our Limits documentation.
| Capability | Status | Note |
|---|---|---|
| S3 API (SigV4, presigned URLs, multipart) | Available | Tested with aws-cli, boto3 and rclone. |
| Data in Indonesia (id-jkt-1) | Available | Dalang Data Center Pandeglang, Banten. |
| Capacity above 50 GB per account | By contract | Through sales; from 1 PB as an annual contract with a special price. |
| Objects above 100 MB | Planned | Waiting on a TLS origin and Cloudflare Full (Strict). |
| Object replication | Available | Two copies in separate racks; no object backup, HA or SLA. |
| A written SLA | Not available | Not yet. |
| Versioning, object lock, lifecycle | Not available | Not yet. |
1
Your volume, read/write pattern and compliance requirements.
2
Capacity estimate, per-TB price and contract terms.
3
Load part of your data and measure it yourself.
4
Capacity is allocated, the account set up, and data migrated with rclone or aws-cli.
Datasets, shards and checkpoints read repeatedly with no egress bill.
Archives and large assets served widely with no bandwidth fee.
Data-location needs in Indonesia and Rupiah billing, through a contract. Not legal advice.
Two Dalang entities, depending on where the customer is. The contracting entity is named on your invoice.
Dalang's operating company in Indonesia: it runs the infrastructure, operates Dalang Data Center Pandeglang, and issues faktur pajak for Indonesian customer contracts. Indonesian law applies. The dalang.io domain is registered as a PSE Privat with Komdigi in this entity's name (since 19 June 2025).
The Dalang group parent, based in Singapore (UEN 202622331M). Singapore law applies to contracts with this entity.
Not as a self-serve product. The account quota is 50 GB now. From 1 PB, capacity is sold as an annual contract through the design-partner programme, and we state the technical readiness openly on this page.
From 1 PB, a special price from our sales team in an annual contract, based on volume and term. The self-serve list price is Rp396 per GB per month NET and is a reference only.
T4 data is stored in Dalang Data Center Pandeglang, Banten, Indonesia. Your legal and contractual requirements are covered in the contract process; we do not give legal advice.
Yes, because T4 is S3-compatible: rclone or aws-cli copies from the source into T4. Egress charges from the source provider still follow that provider.
Customers in Indonesia contract with PT Mashanz Sumber Terbuka (Indonesian law and faktur pajak); international customers with Dalang Pte. Ltd. in Singapore (Singapore law). The contracting entity is named on your invoice and on Dalang's Legal page.
Tell us your volume and requirements. We reply with the next step.