Pricing & billing

Rates

Rp396 / 720 hours = Rp0.55.

How it is measured

T4 takes one sample per hour: how many bytes you stored during that hour. Bytes per hour are called byte-hours.

NET = byte-hours × Rp0.55 / (1 GB × 1 hour)

Example: 50 GB for 30 days (720 hours):

byte-hours = 50 × 720 = 36,000
NET        = 36,000 × Rp0.55 = Rp19,800
PPN        = truncate(19,800 × 11 / 100) = Rp2,178
Total      = Rp21,978

When it is charged

• Usage is measured hourly, but the credit debit is monthly: one

platform-priced quote per user and period, containing NET and PPN 11%.

• The platform computes the amount from the month's byte-seconds; T4 never

sends a rupiah amount. Hourly figures are estimates shown on Billing.

• If the balance cannot cover the monthly debit, the invoice is marked unpaid

and writes are blocked until a top-up lets the retry succeed.

Quota, stop and debt

• The account quota is 50 GB of live objects.
• Any positive balance allows writes; there is no minimum balance.
• A monthly debit leaving Rp0/negative stops storage. Unpaid/negative amounts

are debt for 10 days; after that object data is deleted and the invoice remains. Top-up stays available.

Reports

The Billing page shows:

• the period's NET, PPN and total;
• daily byte-hours;
• the monthly debit;
• a Download report (CSV) link for any period.

The CSV contains the date, byte-hours, NET, the debit list and totals — enough for your finance team to re-check the arithmetic.

Not billed

• Objects created and deleted within the same hour (hourly sampling).
• Multipart uploads that never completed (no Complete call).
• Requests, metadata, bucket names and API keys.