Postclic premium unlimited: promotional offer at RM 4.19 for 48h, then RM 228.34 per month without commitment

Cancellation service #1 in Malaysia
Pulumi is a software-as-a-service platform for Infrastructure as Code, or IaC. In simple terms, it lets developers and IT teams create and manage cloud resources using programming languages instead of clicking around manually in cloud dashboards.
For a Malaysian user, this matters because cancelling Pulumi is not the same as cancelling a streaming app. You may still have live AWS, Azure, or Google Cloud resources linked to your Pulumi setup, so stopping the subscription does not automatically shut down your cloud costs.
Pulumi operates through its website and account system. The verified cancellation route is through your account settings on the Pulumi website, where you follow the account termination steps "provided instructions to terminate your account" (pulumi.com).
The free Individual plan is RM0.00 monthly, so many solo users never pay at all. The paid plans start at Team for $39.00 (RM180.00) monthly and Enterprise for $399.00 (RM1,800.00) monthly, based on the research conversion provided.
What people usually pay for is not basic stack usage alone. They pay for team collaboration, CI/CD support, AI assistance with Pulumi Neo, access control, audit logs, SAML or SSO, RBAC, internal developer platform tools, drift detection, and broader enterprise governance features "pricing" (pulumi.com).
If you are on Team or Enterprise, you are normally paying because your organisation needs shared workflows, not just personal infrastructure scripts. That is why cancellation often needs a quick internal check with finance or engineering before anyone clicks anything.
Pulumi shows official pricing in US dollars on its pricing page, while this guide uses local equivalents in ringgit for clarity. The plans in the research data are listed as Individual RM0.00, Team $39.00 (RM180.00), Enterprise $399.00 (RM1,800.00), and Business Critical with custom pricing (pulumi.com).
There is no verified local Malaysia billing page, local Bahasa Malaysia support page, local customer service phone line, or local office contact in the available source set. Support is routed through community channels and paid support options, and there is no live chat listed "No live chat available" (pulumi.com).
If you signed up from Malaysia, the practical takeaway is senang enough: manage the subscription online, save your records in English, and do not expect a Malaysia-specific cancellation hotline.
Pulumi uses a freemium structure. Individual is free, while Team and Enterprise are paid, and the service terms say the agreement renews automatically for another period equal to the initial term unless either party asks to terminate at least 30 days before the current term ends.
That 30 day timing can catch teams off guard. Many users worry about being charged after cancelling, and that concern is fair because if your order form has a term commitment, waiting until the last minute may be too late for the next renewal cycle.
Pulumi also offers a 14 day money-back guarantee for Team and Enterprise Editions, with a refund request allowed within 14 days of purchase "no questions asked" (pulumi.com). That is useful, but it is not the same thing as a standing right to prorated refunds later in the subscription.
A lot of users feel annoyed when the cancellation path is unclear, and even more stressed when they worry they may lose access too early. Before doing anything, note your billing date, capture your current plan page, and save any data or configuration your team still needs.
At minimum, take screenshots of your account settings, subscription level, active organisation details, and the date shown for the next bill. If you are on Team at $39.00 (RM180.00) monthly or Enterprise at $399.00 (RM1,800.00) monthly, one wrong renewal can be expensive enough to hurt.
Also check whether you still have stacks tied to cloud resources. A subscription cancellation and an infrastructure destroy are different things. If your AWS resources are still running, your cloud provider can continue charging you even after Pulumi access changes.
The only verified cancellation method from the research is through the Pulumi website account settings. Pulumi states that to cancel your account, you should go to your account settings on the website and follow the instructions there to terminate the account (pulumi.com).
The exact button labels are not published in the verified source set, so the safest click path is this practical route: sign in on the Pulumi website, open your account area, go into settings, then look for billing, subscription, organisation, or account termination options. If your workspace has multiple organisations, make sure you are cancelling the correct paid one.
Open the support page as a backup while doing this: Pulumi support options. Since there is no verified live chat or phone line, this page is your best official starting point if a cancellation control is missing from the dashboard.
No dark pattern was identified in the research, which is good news. There is no verified evidence that Pulumi hides the cancellation path behind repeated retention popups or forced chat queues.
Even so, watch for a common SaaS issue: cancelling a user account is not always the same as cancelling a paid organisation subscription. If your team uses a shared workspace, remove any confusion by checking the billing owner, the order form term, and whether your cancellation applies to the whole organisation or only your personal login.
If a confirmation page appears, screenshot it immediately. If an email confirmation arrives, save it as a PDF. This is the proof you will need if a later charge appears on your card statement.
Pulumi does not list a customer support phone number in the verified support source. It also does not list live chat, and no direct support email is specified in the available data "support is provided through community channels and paid support options" (pulumi.com).
That means the realistic approach is to use the support documentation page and any paid support route attached to your plan. If you are in a company setting, also ask your account owner or procurement team whether there is an order form or enterprise contact involved, because the terms mention service terms and automatic renewals tied to that form.
The support hours are not specified in the verified material. If you are trying to stop an imminent renewal, do not wait until the final day and hope for a same-day manual fix.
No physical cancellation address was found in the verified material, so online cancellation remains the main route. If you still need stronger proof for an internal audit trail, you can send a registered written notice to any official business address you can verify independently from Pulumi corporate materials, but this guide cannot provide one because none was found in the approved source set.
Some Malaysian users prefer a trackable written record when the renewal deadline is close. A digital registered delivery service such as Postclic can also create timestamped proof of sending, receipt, and opening, which may be easier than lining up at the post office.
Use written notice as a backup, not as your only move. Do the web cancellation first, then keep the written proof if your finance team wants a complete file.
This is where many people get nervous. They do not want to be charged again, but they also do not want access to disappear halfway through the month. The available source set does not publish an exact day-by-day access timeline after cancellation, so Pulumi does not clearly state in the verified links whether access ends immediately or runs to the end of the billing period.
What is confirmed is that the contract renews automatically unless termination is requested at least 30 days before the end of the current term. In practice, if you are on a fixed service term through an order form, cancellation timing matters more than with a casual monthly app subscription.
The terms say the agreement automatically renews for additional periods equal to the initial service term unless either party requests termination at least 30 days before the current term ends. If your initial term is monthly, renewal can roll monthly. If it is annual, the next annual cycle may also roll over.
That is the biggest financial risk with Pulumi. A missed deadline on Enterprise at $399.00 (RM1,800.00) monthly or a custom Business Critical contract can become a much larger procurement issue than a normal consumer subscription.
Pulumi states that after termination it will provide a reasonable opportunity to retrieve your content and cloud applications. The phrase "reasonable opportunity" is useful, but it is not a specific number of days, so do not gamble on a long grace period.
Export or copy anything critical before cancelling. Save stack configuration, state references, deployment history you still need, internal compliance logs, and any organisation settings your team may need for migration.
Also separate Pulumi account closure from infrastructure cleanup. Closing the SaaS account does not guarantee that AWS, Azure, or Google Cloud resources are destroyed. If those resources stay live, the cloud vendor can still bill you.
Pulumi offers a 14 day money-back guarantee for Team and Enterprise Editions. The wording in the research is straightforward: if you are not satisfied with the purchase, you can request a refund within 14 days of purchase, no questions asked (pulumi.com).
This is the strongest refund fact in the available source set. No cancellation fee was found in the Terms of Service, and no early termination fee was found either, which is helpful if you are worried the company may bill an extra exit penalty.
Outside that 14 day guarantee, the verified material does not promise prorated refunds for partially used billing periods. So if you cancel late in the month, assume you may stop renewal going forward but may not recover the already billed period.
In Malaysia, subscription and service cancellation issues are mainly framed under the Consumer Protection Act 1999, or CPA. The CPA does not create one universal cooling-off period for every online subscription, but direct sales contracts can carry a 10 working day cooling-off period if the legal conditions for direct sales are met.
For Pulumi, the more practical refund right is Pulumi's own 14 day money-back guarantee for Team and Enterprise. That is actually better than relying on a general assumption that all digital subscriptions in Malaysia must have a cooling-off period, because they do not.
If the charge was unfair, misleading, or continued after a valid cancellation, you can escalate a complaint to KPDN and, where suitable, file a claim with the Tribunal for Consumer Claims Malaysia, known as TTPM.
Move fast if you are within the 14 day window. Log in, take a screenshot of the purchase date, the plan name, and the amount, then use the Pulumi support route documented at Pulumi support.
Your refund request should include the account name, organisation name if relevant, invoice or transaction reference, purchase date, amount charged, and a clear line saying you are requesting a refund under Pulumi's 14 day money-back guarantee for Team or Enterprise. Ask for written confirmation in the same thread.
If there is no response, send a follow-up before day 14 ends. The best evidence is a timestamped request made inside the refund window, not a later explanation that you intended to ask earlier.
If you cancelled properly or requested a valid refund and still got charged, you can ask your card issuer for a chargeback. In Malaysia, people usually call this disputing an unauthorised or recurring card transaction with the bank, and the typical timeframe is around 60 to 120 days from the transaction date or from when you discovered the problem.
This sits within Bank Negara Malaysia's complaint-handling framework and the Financial Services Act 2013 or Islamic Financial Services Act 2013, depending on the institution. Bring screenshots, confirmation emails, invoice dates, and any support ticket record, because the bank will ask for proof.
No verified App Store or Google Play Pulumi subscription path was established in the approved source set, so do not assume mobile store refund rules apply here.
The terms say the agreement "automatically renews for additional periods equal to the initial service term unless either party requests termination at least 30 days prior to the end of the current term" (pulumi.com). That single line matters a lot more than fancy feature lists.
The commitment duration is described as the initial service term specified in the order form, then renewed for additional periods of the same duration. If your company signed an annual order form, a last-week cancellation attempt may miss the deadline.
No specific free trial conversion terms were found in the Terms data provided. So if you are cancelling after a test phase, do not rely on assumptions. Check your order form, invoice date, and whether the paid subscription already started.
On data access, Pulumi says it will provide a reasonable opportunity to retrieve your content and cloud applications after termination. That sounds fair, but because there is no exact day count in the verified data, export everything before cancelling.
The terms say Washington State law governs the contract, and disputes are resolved through binding arbitration in Seattle, Washington, USA, under American Arbitration Association rules. For a Malaysian customer, that is not practical for a small billing dispute.
If the issue is a consumer billing problem, your realistic local path is still to document everything and approach KPDN, TTPM, your bank, or all three depending on the amount and payment method. For a normal subscription dispute, local escalation is more useful than arguing abstract overseas forum clauses.
| Plan | Price (USD / MYR) | Billing period | Main features |
|---|---|---|---|
| Individual | RM0.00 | Monthly | 1 user, unlimited projects |
| Team | $39.00 (RM180.00) | Monthly | Up to 10 users, CI/CD |
| Enterprise | $399.00 (RM1,800.00) | Monthly | Unlimited users, SAML, audit logs |
| Business Critical | Custom (Custom MYR) | Monthly | Self-hosting, compliance, automation |
The cheapest plan is clearly Individual at RM0.00 monthly. The highest published recurring price in the verified data is Enterprise at $399.00 (RM1,800.00) monthly, while Business Critical is custom and could be higher depending on the contract.
If you are reading this because a surprise renewal landed on your finance report, Team and Enterprise are the plans to inspect first. Those are also the plans covered by the 14 day money-back guarantee in the verified research.
The available pricing data here is monthly only, and no annual discount figure was provided in the approved source set. There is also no verified price increase history in the material provided for this guide.
No cancellation fee or early termination fee was found in the Terms. That is good. The bigger cost risk is not hidden exit charges but forgetting the auto-renewal deadline in an order form.
In Malaysia, the key law is the Consumer Protection Act 1999. It does not give a blanket cooling-off right for every online SaaS subscription, but it does regulate unfair practices and supports complaints when charges, representations, or service handling are improper.
For direct sales contracts, Malaysia provides a 10 working day cooling-off period when the contract meets the required conditions, including written form and the specific cooling-off statement. That rule is useful to know, but many Pulumi subscriptions may not fall neatly into that direct sales category.
Pulumi's 14 day money-back guarantee for Team and Enterprise is the clearest refund path available from the verified source set. For many Malaysian users, that company promise will be easier to use than arguing over whether the CPA direct sales cooling-off model applies.
If Pulumi accepted your money, you requested cancellation or refund within the published period, and the company still billed you or ignored you, then KPDN and TTPM become practical escalation channels. Plainly put, if the service side does not sort it out, you can take the paperwork local.
Start with your evidence file. Include screenshots of the plan, the cancellation page, your refund request, invoice dates, card statement entries, and any support thread. If the issue is under the 14 day guarantee, highlight the purchase date and the date you asked for the refund.
Then submit a complaint to KPDN through its consumer complaint channel, and consider TTPM if you are claiming a specific amount back. If the payment was by card, file the dispute with your issuing bank on the same day rather than waiting for the company to reply indefinitely.
For consumer escalation, start with the Ministry of Domestic Trade and Cost of Living, known as KPDN, and the Tribunal for Consumer Claims Malaysia, known as TTPM. This guide cannot add unverified phone numbers or addresses beyond the approved source set, so use their official government portals when filing.
For banking disputes on recurring card charges, contact your issuing bank directly and refer to the transaction as an unauthorised or recurring card dispute. Most banks work within a rough 60 to 120 day chargeback window, depending on card network rules.
Verdict: based on the limited review sample available here, cancellation-related experiences lean negative. The general sentiment is 0 positive and 2 negative out of 2 unique reviews, and both negative comments focus on difficulty stopping or deleting infrastructure cleanly rather than a hidden billing trap.
That distinction matters. No dark pattern was identified in Pulumi's account cancellation flow, but users can still struggle when stacks are tied to AWS resources or provider errors block the destroy process. In Malaysia-specific research, no local issue trend was identified.
| Theme | Frequency | Typical example |
|---|---|---|
| Stack deletion difficulty | 1 review | AWS-linked stack stuck |
| Destroy process errors | 1 review | Provider error blocks exit |
| Billing complaints | 0 reviews | No sample found |
| Source | Rating | Number of reviews |
|---|---|---|
| Stack Overflow | Negative trend | 2 |
Since only negative review examples were available in this dataset, the balanced takeaway is this: the published account cancellation route looks straightforward, but technical teardown can still be messy if your infrastructure dependencies are not cleaned up properly.
Save a screenshot of your current Pulumi plan, your billing date, and the organisation or workspace name. If the account is paid, also save the last invoice showing Team at $39.00 (RM180.00) or Enterprise at $399.00 (RM1,800.00).
Export any stack configuration, deployment history, and team settings you still need. Because Pulumi only promises a reasonable opportunity to retrieve content after termination, it is smarter to save everything before you click cancel.
Prepare the transaction date, amount, card statement reference, invoice ID, and the exact date you submitted the refund request. For the 14 day guarantee, dates are everything.
If your company paid through procurement, save the order form too. The service term and the 30 day non-renewal deadline may be written there.
Keep the cancellation confirmation screenshot, the confirmation email if any, and a PDF copy of the support request. Then check your next card statement when the usual billing date passes.
If a new charge appears after cancellation, you will need these documents for KPDN, TTPM, or your bank dispute.
This is the biggest practical mistake. A user may cancel Pulumi and assume all related cloud charges will stop, but Pulumi manages infrastructure definitions, while AWS or other providers bill for live resources separately.
The review saying "I can't delete a Pulumi stack tied to AWS resources." (Stack Overflow) shows exactly how this problem appears in real life. Solve it by auditing your cloud resources before account closure.
If your service term renews automatically and the contract requires 30 days notice before the end of the term, waiting until the last few days is risky. This matters more for Team, Enterprise, and custom contracts than for the free tier.
A realistic scenario is a finance manager spotting a renewal one week before the contract end date. By then, the account owner may already be too late for the next cycle if the order form follows the stated renewal clause.
The 14 day money-back guarantee is useful only if you act inside that window. Some users cancel first, then wait for an internal approval to ask for the refund, and that delay can kill the claim.
Do both quickly: submit the cancellation and the refund request together, then save proof of the timestamp. If you bought Team at $39.00 (RM180.00), that is manageable. If it is Enterprise at $399.00 (RM1,800.00), delay gets expensive fast.
Even when a cancellation flow is simple, never leave without screenshots. There is no verified dark pattern here, but payment disputes are much easier to win when you have the account page, the request date, and the confirmation.
If support later says they cannot locate the request, your evidence file becomes the whole game, lah.
The review mentioning a "Terraform AWS Provider error" (Stack Overflow) suggests another common mistake. Users focus only on the Pulumi dashboard when the real blocker sits in a provider configuration, credentials issue, or infrastructure dependency chain.
If destroy fails, inspect the cloud provider setup, state references, permissions, and plugin versions. Cancelling the SaaS account will not magically fix a broken stack teardown.
| 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 |
The verified route is web or account settings, so that is the practical method most users should try immediately. Registered written notice is slower but gives stronger paper proof if your organisation needs an audit trail.
The table includes App Store and Google Play because it was supplied in the required method data, but no verified evidence in the approved source set confirms Pulumi subscriptions are commonly managed there. For this service, the website route is the one supported by the research.
Right after cancelling, save the confirmation page and set a calendar reminder for your next expected billing date. Then log back in once to confirm the plan or account status reflects the change.
If your subscription was cancelled near the end of a term, check whether access remains available through that period. Since Pulumi does not clearly publish the exact post-cancellation access timeline in the verified links, verify it directly from your account status.
Watch at least the next one to two statement cycles, especially if the usual bill date is close. Look for the exact merchant descriptor and amount matching your previous Pulumi charges.
If an unauthorised recurring charge appears, contact your issuing bank and ask to dispute it as a recurring or unauthorised card transaction. In Malaysia, this is usually handled as a chargeback within roughly 60 to 120 days, depending on bank and card rules.
Terraform is the obvious alternative if you want a widely used open-source IaC tool with optional enterprise support. OpenTofu is another strong choice if you want a community-driven fork with compatibility in that ecosystem.
If your team is mostly on AWS, AWS CloudFormation or AWS CDK may be simpler because they align directly with AWS workflows. Crossplane is worth a look if your operations already revolve around Kubernetes.
No physical cancellation address was found in the verified material used for this guide. That means this is effectively an online-first cancellation process, with the account settings page as the confirmed route.
If your company policy requires written notice, use the online cancellation first and then pair it with a separately verified written notice method for your records. Do not rely on an unverified address copied from random third-party sites, can or not, because that can create more trouble than it solves.
For most Malaysian users, the fastest path is simple: cancel from the Pulumi website, save every screenshot, request any eligible refund within 14 days, and monitor your card statement after the next billing date. If Pulumi ignores a valid request or keeps charging, escalate to your bank, KPDN, and TTPM with a clean evidence file.
That is the no-nonsense route. It is not glamorous, but it is the one that usually saves time, money, and unnecessary headache.
Already sent a letter? Enter its tracking number to see its proof of dispatch and certified timestamp.