Postclic premium unlimited: promotional offer at ₱61.60 for 48h, then ₱3,353.56 per month without commitment

Cancellation service #1 in Philippines
Pulumi is a software platform for infrastructure as code. It lets developers define and manage cloud resources with programming languages instead of only declarative templates. The company is based in Seattle, United States, and the official terms page and pricing pages are published on pulumi.com.
For users in the Philippines, the key point is simple: Pulumi is not a consumer app with an in-app cancel button. It is a SaaS product sold through the web, and the official source says cancellation should be handled by contacting support directly through its support form at support.pulumi.com.
The free entry point is strong. Pulumi lists an Individual Edition at ₱0.00 per month, and the paid model mainly starts when teams manage more cloud resources and need shared billing, support, access control, and advanced organization features "for your whole team" (pulumi.com).
Team pricing is usage-based rather than a simple flat monthly fee. Pulumi states Team Edition is priced at $1.00 (₱56) per 2,000 credits, with 150,000 free credits each month, which can cover up to around 200 cloud resources for free in many cases (pulumi.com). Enterprise pricing is custom.
If you are in the Philippines, heads up: there is no evidence in the verified sources of PHP billing on the checkout page, local customer support hours, a Philippine office, GCash support, or Maya support. Published pricing is in US dollars, so I converted the figures into pesos using 1 USD about ₱56.5, as requested.
There is also no verified App Store or Google Play subscription route for Pulumi. That matters because many users waste time searching iPhone or Android subscription menus. For Pulumi, the available evidence points to a web account and support request flow, not mobile store billing.
Many Pulumi users get frustrated because the process is not clearly laid out in a simple account path, and some users have reported confusion when the console showed an annual subscription unexpectedly (archive.pulumi.com). Before you cancel, take five minutes to gather proof so you do not end up arguing about the billing cycle later.
The truth is, Pulumi's cancellation path is more manual than it should be. Since the verified source does not provide a public click path such as Settings > Billing > Cancel, your best protection is documentation before you contact support.
The official cancellation route in the available sources is to contact Pulumi support directly (pulumi.com). Use the support request page here: Pulumi support request form. This is the most concrete verified channel available.
When you open the request form, include your account email, organization name, current plan, and the exact sentence that you want the paid subscription canceled before the next billing date. Ask for two things in one message: cancellation confirmation and written confirmation that no further recurring charge will be attempted.
A good message is short and specific. Example: “Please cancel our Pulumi Team subscription for organization X before the next billing date on April 15, 2026. Please confirm in writing that recurring billing will stop.” That wording reduces back and forth.
Pulumi does not list a public support phone number in the verified support data. There is also no live chat listed, and no public support email address is specified. The practical result is that the support form is the real working channel for most users.
If you need a paper trail outside the form, you can also send a registered letter to the company address listed later in this guide. Some users in the Philippines prefer this when the billing amount is significant. A digital alternative such as Postclic can also create time-stamped proof of sending, receipt, and opening without going to a post office.
Do not look for an App Store or Google Play subscription if you signed up directly on pulumi.com. The verified sources say Pulumi does not offer a mobile application through App Store or Google Play for this purpose, so those cancellation routes are not applicable here (pulumi.com).
Do not assume that deleting projects or stopping cloud resources automatically cancels billing. Pulumi pricing is tied to managed resources and credits, but subscription closure still needs an explicit support request. If you skip that step, you may still have an active paid plan.
Pulumi's terms in the verified sources do not clearly spell out the exact access cutoff after cancellation. Because of that, the safest assumption is that support will process the request and tell you the effective end date in writing. Ask them to confirm whether access continues until the end of the current billing period.
If you do nothing, the risk is simple: billing may continue under your existing paid setup because the terms do not clearly state a public auto-renewal rule, and the pricing model is ongoing for team usage (pulumi.com). That is why your cancellation request should mention the next invoice date explicitly.
The verified terms do not clearly explain data retention after cancellation (pulumi.com). In plain language, Pulumi does not publicly tell you on the cited terms page how long organization data, logs, or project information stays available after closure, so you should export anything important before sending the cancellation request.
If your team relies on stack history, configuration references, or audit-related records, save them locally before the account changes. This matters even more for enterprise or team admins, because once billing access changes, recovering data can become slower and support-dependent.
Here is the short version: Pulumi's Terms of Service do not spell out a clear refund policy for general cancellations, unused periods, or billing errors in the verified research data (pulumi.com). That is frustrating, especially if you are trying to stop a charge quickly and want a clear answer on prorated refunds.
Because the terms are silent on this point, refunds appear to be handled case by case through support. If you were charged after sending a cancellation request, include the request date, invoice amount, and screenshot proof in the same support thread. That gives you the best chance of getting a clean answer.
In the Philippines, there is no universal statutory cooling-off period for all online subscriptions. The local rule often cited for a seven working day cooling-off period is tied to door-to-door or direct sales, not all digital SaaS purchases. For Pulumi, that means you usually cannot rely on an automatic seven day online refund right under RA 7394 alone.
Still, the Consumer Act of the Philippines or Republic Act No. 7394 gives you protection against unfair or misleading sales practices. If you were charged after a valid cancellation request, or if billing terms were unclear, you can escalate a complaint to the Department of Trade and Industry or DTI.
If support does not respond or denies a charge you believe was unauthorized, contact your bank, credit card issuer, GCash, or Maya. In the Philippines, cardholders typically have up to 60 days from the statement date to dispute a transaction under BSP complaint practices. Save every screenshot before starting a chargeback.
The official terms page is here: Pulumi Terms and Conditions. Based on the verified data, the terms do not clearly specify an auto-renewal clause, minimum commitment duration, data retention after cancellation, governing law, or dispute resolution procedure in a way that answers a cancellation question directly.
That gap is important for users in the Philippines. If the terms do not tell you exactly whether billing renews automatically or how unused time is treated, your best move is to request written confirmation from support before the next billing date and keep that message as evidence.
Pulumi does offer a free individual tier for private projects, and its team plans may include free trials or free monthly credit allowances depending on the edition, but the exact conversion mechanics into paid billing are not fully detailed in the verified research set (pulumi.com). So if your organization moved from free usage into billable usage, check the billing history carefully.
A practical tip here is to capture the page showing included free credits and current consumption before you cancel. If the bill came from usage exceeding the free monthly allowance, that screenshot helps you understand whether the invoice is consistent with Pulumi's published pricing model.
Plan | Price (USD / PHP) | Period | Main use |
|---|---|---|---|
Individual Edition | ₱0.00* | Monthly | Unlimited individual use |
Team Edition | $1.00 (₱56)* | Per 2,000 Credits | Team resource management |
Enterprise Edition | Custom* | Custom | Large organizations |
Prices marked with an asterisk are approximate conversions from USD using 1 USD about ₱56.5. Check the official pricing page for exact current pricing and billing terms.
The least expensive published option is Individual Edition at ₱0.00. The most expensive is Enterprise Edition, which is custom priced and typically aimed at large organizations needing advanced security, policy, access control, support, and billing options (pulumi.com).
For many small teams, the biggest billing surprise is not a flat monthly fee but resource-based usage beyond the free monthly credits. If your workloads are modest, you may be paying for a Team setup you no longer need. In that case, moving back to the free individual tier or to another IaC tool may cut costs fast.
Pulumi's pricing blog describes a usage-based approach for teams "for your whole team" rather than a simple seat-only subscription (pulumi.com). That means your invoice can change with resource volume. If you cancel, ask support whether any pending metered usage will still be invoiced after the request date.
The verified sources also mention a local complaint where a user believed the console showed an annual subscription unexpectedly (archive.pulumi.com). If your account displays annual billing and you did not expect that, screenshot the page before support changes anything.
For users in the Philippines, the main law to know is the Consumer Act of the Philippines or Republic Act No. 7394. It does not give a universal online subscription cooling-off period for every SaaS purchase, but it does protect consumers against unfair, deceptive, or misleading practices and supports complaint filing with the DTI.
Pulumi's terms do not clearly spell out key cancellation rules such as auto-renewal or refunds in the verified data. If billing continued after you clearly asked to cancel, that mismatch can strengthen your complaint because your evidence will show the request date, billing date, and the amount charged.
The seven working day cooling-off period commonly discussed in Philippine consumer guidance is tied to door-to-door or direct sales. For an online software subscription like Pulumi, there is no broad automatic cooling-off rule confirmed in the provided verified sources. So your strongest route is proof-based negotiation with support, then escalation if needed.
If you subscribed due to unclear representations or saw billing behavior that did not match what you understood at signup, explain that in plain language. DTI complaints work better when you show screenshots, dates, and exact amounts instead of broad accusations.
For payment disputes, BSP complaint channels and your issuing bank matter because chargebacks are usually time-sensitive. In the Philippines, users commonly have up to 60 days from the statement date to dispute an unauthorized or continued charge, so do not let the billing cycle sit for months.
For consumer subscription complaints, contact the Department of Trade and Industry. For banking or card disputes, contact the Bangko Sentral ng Pilipinas through your bank's dispute process first, then escalate if needed. Pulumi itself does not list a Philippine office in the verified sources.
Based on the verified material available for this guide, cancellation looks more difficult than easy. The reason is not a proven dark pattern, because none was identified, but a lack of clear self-service steps plus at least one public report of billing-plan confusion in the console (archive.pulumi.com).
The review sample in the supplied dataset is weak and mostly unrelated to Pulumi, so I am not using those off-topic quotes as evidence about Pulumi itself. For Pulumi specifically, the best verified user signal is a negative support-seeking report about cancellation difficulty. So the fair conclusion is limited but honest: the process appears unclear, not impossible.
Theme | Frequency | Typical example |
|---|---|---|
Unclear cancellation path | Reported | Needs support request |
Billing plan confusion | Reported | Annual plan shown |
No live chat | Confirmed | Form only support |
Source | Rating | Number of reviews |
|---|---|---|
archive.pulumi.com | Negative signal | 1 public thread |
pulumi.com | Neutral | Official policy pages |
Prepare evidence before opening the support form. This should include a screenshot of the plan page, the billing overview, your organization name, and the next charge date. One clear image can save days of back and forth if support asks which account should be closed.
Refund cases are easier when you provide exact transaction details. Include the invoice ID, charge date, charge amount, payment method, and the cancellation request timestamp. If your bank statement shows the PHP amount, include that too, even if Pulumi billed in dollars.
After cancellation, save the reply from support and a screenshot of the closed ticket page if available. If a later charge appears, those files become your best evidence for DTI, your bank, GCash, Maya, or your credit card issuer.
A common mistake is sending the cancellation request on the same day the invoice is due. Since Pulumi relies on support contact rather than a visible one-click cancel flow in the verified sources, same-day requests are risky. Send the request several days before the next charge date and ask for written confirmation.
Real-world scenario: your billing date is May 30, but you write support on May 30 at night Manila time. If billing runs earlier in another time zone, the charge may already be processed before anyone sees your ticket.
Some users stop using the service and think that means the paid plan ends automatically. That is not safe. Usage may drop, but plan status and recurring billing can remain active until support processes a cancellation request.
The solution is simple: pair operational cleanup with a billing closure message. Delete or archive what you need, then immediately send the support request that says the paid subscription must end before the next billing date.
The archive thread shows a user confused by an annual subscription display (archive.pulumi.com). If something on your billing screen looks wrong, do not rely on memory. Capture the exact page, date, and account identifier before support edits the account.
This is especially useful if you later argue that the displayed plan did not match your understanding. Without screenshots, the dispute becomes your word against the platform record.
Pulumi's published terms in the verified data do not clearly promise prorated refunds for unused periods. If you cancel halfway through a billing cycle, do not assume money comes back automatically. Ask directly in the same cancellation ticket whether any unused charges will be credited or refunded.
If the answer is no and you believe the charge happened after cancellation, that becomes a payment dispute issue rather than a routine refund. At that point, your next step may be your bank or e-wallet provider.
Method | Notice period | Fee | Difficulty |
|---|---|---|---|
Web/account | Before next billing | No fee found | Easy |
App Store (iOS) | Before next billing | No fee found | Medium |
Google Play (Android) | Before next billing | No fee found | Medium |
Registered mail | 5-10 business days | No fee found | Higher, best proof |
For Pulumi, the practical route is the web support form because that is the verified official channel. Registered mail adds stronger proof if the amount is large or support is unresponsive. The App Store and Google Play rows are included only for comparison, but for Pulumi itself they are not applicable based on the verified sources.
No cancellation fee or early termination fee was found in the terms data. That is good news, but it does not replace the need for written confirmation that billing has actually stopped.
Once you send the request, save the ticket number immediately and take a screenshot of the submission success page. If support replies, keep that email in a dedicated folder. Set a calendar reminder three days before the next billing date and another one on the billing date itself.
If the end date is not mentioned in support's reply, ask again. You want one line in writing that states the effective cancellation date and whether the account remains active until the current billing period ends.
Check your card, bank, GCash, or Maya activity for at least one full billing cycle after cancellation. If a continued or unauthorized charge appears, contact the payment provider quickly. In the Philippines, cardholders typically have up to 60 days from the statement date to dispute a transaction through the bank or issuer, with BSP-related escalation if needed.
DTI handles consumer complaints for online subscriptions under RA 7394. Use your cancellation screenshot, support reply, invoice, and statement entry as evidence. If you do not keep proof, the chargeback process becomes much harder.
If you are leaving Pulumi only because of billing friction, there are solid alternatives. Terraform is still the best-known IaC option and has a free entry path. OpenTofu is a community-driven Terraform-compatible option and is free. Crossplane works well for Kubernetes-centered infrastructure management.
Ansible is another free option if your needs are closer to automation and configuration management than full cloud state handling. Your choice depends on whether you want programming-language workflows, declarative configs, or Kubernetes-native control.
If you want to send a formal cancellation notice by post, use this address:
This is useful when you want extra proof beyond the support form, especially for enterprise or team billing disputes. Allow around 5 to 10 business days for delivery and record keeping.
Use the support form and the postal address together if the amount involved is high or if support has not replied before your billing date. Send a short letter with your account email, organization name, billing date, and a direct cancellation instruction. Keep a copy of the letter and proof of dispatch.
For most users, the online support request is still the fastest operational channel. The mailing address is a backup option with stronger evidence value, not a replacement for the support ticket.
Already sent a letter? Enter its tracking number to see its proof of dispatch and certified timestamp.
Written by Sofia Lim
Former postal advisor · 4 years experience
Former postal-services advisor and e-signature specialist, I have been writing for Postclic for 4 years to demystify legally binding mail for everyday users.