Turn supported Make automations into source code you control. Assess compatibility with your consent, verify defined behavior, then deploy to your own Cloudflare account.
With your consent, the blueprint is sent to our private engine for an ephemeral compatibility check. Remove secrets before upload.
Drag a JSON export into this space, or browse to select a file.
or press ⌘O to select a file
Enter actual avoidable charges. A blueprint alone cannot establish your invoice savings.
Compare the generated Worker with an independent subset interpreter using mocked HTTP responses.
Requires a supported blueprint. Supply JSON replay cases with mock HTTP responses. The server never invokes real external endpoints.
Create an account, confirm financial eligibility, compile a tested asset, and unlock it after payment.
Accounts are password-protected. Password recovery and verified email enrollment are not yet available.
Requires a compatible blueprint, a 3:1 customer-assumed cost benefit, and replay fixtures. Choose the $199 single-workflow tier in the calculator above. The $499 bundle covers 3–10 supported workflows and currently uses the API, not this button. This is not certified Make parity.
Sign in to view orders and authorized downloads.
Find out whether your workflow is supported for free. Pay only for an accepted, replay-verified source-code package.
Single workflow: $99 beta / $199 standard.
Bundle of 3–10 supported workflows: $199 beta / $499 standard.
Compatibility assessment is free. Beta prices require a valid, activated invitation code. Checkout remains disabled during live-payment validation.
Founding Beta · activated invitation onlyStandard price: $199
One compatible Make scenario, compiled to an independently deployable Cloudflare Worker project.
Founding Beta · activated invitation onlyStandard price: $499
Three to ten supported workflows, each delivered as an independent Worker project.
Bundle compilation currently uses the API; the page’s purchase button supports single workflows.
Cloudflare infrastructure, third-party API use, deployment and ongoing maintenance may have separate costs. Savings are not guaranteed. Stripe checkout is activated only after launch testing.
Independent source code, explicit limits and a verifiable handover—rather than another workflow-platform migration.
DECOMMISSION is a deterministic No-Code-to-Serverless Compiler. It translates supported Make.com JSON blueprints into standalone, customer-owned TypeScript projects designed to run on Cloudflare Workers.
It is not another automation platform, an n8n workflow converter, or an AI prompt wrapper. It compiles supported visual workflow logic into executable source code, using strict validation rather than speculative code generation.
Unsupported workflow semantics are rejected rather than silently approximated.
The distinction is the execution model.
n8n and Activepieces are automation engines, with hosted and self-hosted deployment options. Self-hosted editions can reduce software licensing expenses, but you still operate an automation engine.
DECOMMISSION removes that engine from the execution path for workflows within its supported Make.com subset. The output is a TypeScript project deployed to your Cloudflare account, not a scenario running inside another hosted workflow platform.
DECOMMISSION does not currently claim to convert n8n or Activepieces workflow formats.
Not to execute a successfully migrated workflow.
Once deployed, the generated Worker runs independently. It does not contact DECOMMISSION for licensing, compilation, or execution, and it does not rely on Make.com's workflow engine.
There is no ongoing DECOMMISSION subscription to execute your compiled workflow. You remain responsible for Cloudflare usage charges, third-party API costs, secrets, monitoring, maintenance, and any Make.com workflows you choose not to migrate.
Release C supports a deliberately restricted subset of Make.com scenarios, including supported webhook triggers, HTTP requests, conditional routers, and defined JSON and variable transformations.
DECOMMISSION validates module types and semantics before preparing a paid artifact. Unsupported or ambiguous behavior is rejected.
Complex loops, database change-data capture, arbitrary connectors, unsupported stateful behavior, and multi-system OAuth flows are outside the current guaranteed compilation scope.
This strict boundary is a reliability feature: the compiler must not invent workflow behavior.
Generated Workers include defined runtime safeguards rather than an unprotected sequence of API calls.
Verified capabilities include authenticated webhook execution, bounded retries for eligible transient GET failures, and optional R2 dead-letter storage for failed webhook payloads when the customer configures the required binding. POST requests are not automatically retried, avoiding unintended duplicate side effects.
Durable state, KV-backed cursors, OAuth refresh, API-specific rate limiting, and Slack or Discord alerts are not universal automatically generated features. They require supported semantics or additional customer implementation.
The customer controls deployment configuration, secrets, monitoring, downstream API limits, and operational recovery.
Because the decision is about total avoidable execution cost, not simply the entry-level subscription price.
A single supported conversion costs $199. A supported bundle of 3–10 workflows costs $499. Both are one-time charges rather than recurring DECOMMISSION execution subscriptions.
For example, if a customer can genuinely eliminate $150 in monthly Make charges and expects $10 in replacement monthly operating costs, estimated net savings are $140 per month. A $199 conversion would have an estimated simple payback of approximately 1.42 months.
The calculation is:
Monthly net savings = Avoidable monthly platform charges - Replacement monthly costs
Simple payback in months = Conversion price / Positive monthly net savings
These are customer-supplied assumptions, not guaranteed savings. If the Make bill cannot actually be reduced, there may be no economic case for migration.
DECOMMISSION's eligibility calculation applies a strict 3:1 first-year customer-benefit gate to the supplied estimates.
Cloudflare Workers Paid has a $5 monthly base charge that includes 10 million Worker requests and a separate CPU-time allowance, according to Cloudflare's published pricing.
This does not mean all applications processing 10 million requests will cost exactly $5. Additional CPU usage, R2 or KV operations, storage, and other services can increase costs.
DECOMMISSION reduces dependence on per-workflow automation-engine billing; it does not eliminate infrastructure expenses.
See: https://developers.cloudflare.com/workers/platform/pricing/
DECOMMISSION produces signed provenance materials, including an Ed25519 signature and file-integrity information associated with the compiled artifact.
A customer can verify the delivered files offline against a separately trusted issuer public key and inspect the TypeScript before deployment.
Cryptographic provenance helps detect changes to signed content. It does not, by itself, certify the absence of vulnerabilities, prove functional equivalence, or guarantee that third-party APIs will behave correctly.
You own the customer-specific generated workflow source code and can inspect, edit, back up, self-host, and deploy it independently.
The delivered project includes TypeScript source, deployment configuration, supporting runtime files, tests, and signed provenance materials as applicable to the generated workflow.
DECOMMISSION retains intellectual property in its compiler and pre-existing tooling. Reusable runtime templates embedded in the delivered project are licensed for use with that project under the published conversion license.
The generated Worker does not require a DECOMMISSION license server.
Cloudflare Workers can execute supported webhook and HTTP logic without routing each workflow step through a separately hosted visual automation engine.
That creates a compelling architecture for latency-sensitive and high-volume workflows.
However, DECOMMISSION does not guarantee sub-10ms end-to-end execution, zero cold-start effects, universal uptime, or the absence of downstream API delays. Actual performance depends on the deployed workflow, Cloudflare limits, network conditions, and external services.
Production latency should be measured against the customer's real workload.
Automation agencies and consultants can deliver source-code assets that customers control instead of tying every supported workflow to an ongoing orchestration service.
Technical founders and CTOs can integrate supported webhook and API pipelines into their own Cloudflare infrastructure.
High-volume e-commerce and SaaS operators can evaluate whether removing per-operation workflow-engine charges improves their economics.
The strongest candidates are supported workflows with meaningful, verifiable, avoidable recurring costs.
No. DECOMMISSION's deterministic replay compares defined behavior against supplied test cases and mocked external responses.
It verifies the tested subset and detects selected mismatches. It is not a guarantee of Make production parity. It does not simulate every third-party outage, authentication state, concurrency condition, or production side effect.
Customers should perform independent staging validation before redirecting production traffic.
Selecting a blueprint does not itself upload it. After explicit consent, compatibility assessment sends the selected blueprint to DECOMMISSION's private service for transient processing.
Replay and compilation require separate authorization. Purchased generated ZIP artifacts are stored privately for authorized delivery, while account, order, entitlement, and payment-event records are retained for service operation.
Do not include production credentials or unnecessary personal information in uploaded blueprints.
See the Privacy Policy for the current data-handling disclosures.
Release C has passed automated regression tests and seven release-verification phases.
Cloudflare staging has also demonstrated supported assessment, compilation, signed ZIP generation, private R2 storage, database-backed entitlements, Stripe Sandbox payment fulfillment, permanent webhook delivery, authorized downloads, and refund-triggered entitlement revocation.
These results validate the tested release behavior. They do not constitute certification of arbitrary Make.com scenarios or authorization to begin live payment processing.
You are not buying another place to run your workflows.
You are buying the ability to turn supported rented automation logic into an independently deployable, inspectable, customer-owned software asset.
Compile the workflow. Own the code. Run it on your infrastructure.
