What does it cost to try?
50 renders a month
No card is required at sign-up. Paid plans start at $9 a month for 1,000 renders. One completed output consumes one render regardless of the trigger route; other plan limits still apply.
Affiliate Program
Explain a useful workflow.
Explain a useful workflow.
Earn a recurring share.
Partner with cloudlayer.io and earn half of what they pay recurring commission on every active referral, backed by real-time tracking and monthly payouts.
Full program terms on the affiliate site
How the affiliate program is structured
50% recurring share
Eligible subscription payments continue to earn the published share while the referred account remains covered by the program terms.
Subscription-based earnings
The credited amount follows covered customer payments, including plan changes handled under the program's attribution and adjustment rules.
Referral dashboard
Use the affiliate dashboard to review the tracking events, referred accounts, and earnings data that the program makes available.
monthly payouts
The published minimum is $0. Set up an available payout method and follow the affiliate terms for processing and adjustments.
From enrollment to an attributed referral
1
Apply to the program
Register on the affiliate site, review the terms, and obtain the tracking link assigned to the approved account.
2
Publish useful, disclosed content
Show a real workflow for the audience you serve, link to the relevant product page, and make the affiliate relationship clear.
3
Review credited payments
Use the dashboard to follow attributed referrals and the recurring share on eligible subscription payments.
Start with the workflow your audience already needs
A referral is useful when it connects a real manual step to a specific product workflow. cloudlayer.io is broader than a PDF API: it combines browser-native templates, data collection, rendering, capture, signing, and delivery.
- Design a reusable template. Work visually or edit the supported HTML and CSS source behind the same template.
- Connect the input. Use a hosted form, application request, connector, scheduled public-page capture, or spreadsheet batch.
- Deliver the result. Produce a supported PDF, image, video, or signing workflow and send output through the configured response, storage, or webhook path.
Show the connection between these stages. A tutorial that turns submitted data into a delivered document lets the reader judge the complete workflow, including the integration and operating work it requires.
Keep every product claim sourced and disclosed
An affiliate relationship must be clear, and a product claim should link to evidence the reader can inspect. Use the following boundaries when describing cloudlayer.io.
Claims you can source
- Plan prices, allowances, and limits shown on the pricing page.
- Catalog counts published on the facts page with their source.
- Product behavior described by its product or documentation page.
- Dated comparison claims that still match the cited vendor source.
- Your own clearly labeled experience, including limits or friction you observed.
Claims not published here
- A public uptime percentage or service-level figure.
- A compliance certification or report that is not supplied for review.
- A customer, user, or document count, or a named customer claim.
- A universal speed or latency figure applied to every workload.
- An endorsement that does not clearly disclose the affiliate relationship.
Link to the page that supports the statement. If the product site, documentation, program terms, or your own disclosed test does not support it, do not present it as fact.
Give readers the numbers needed to evaluate fit
Link the free allowance, connector catalog, and SDK list near the workflow you demonstrate. Readers can then confirm cost and implementation fit before creating an account.
Will it fit what I already use?
732 connectors, 727 actions
The integrations catalog names each action so a reader can check the required trigger or operation. The forms page also lists 35 supported payment gateways.
Can I do it from code?
8 official SDKs
The SDK repositories are public on GitHub. Link the language-specific documentation and package so a developer can inspect the supported methods before choosing it.
Use a template or comparison as the concrete entry point
A generic product announcement asks the reader to invent a use case. A working template or a sourced comparison begins with a question they may already be researching.
- Start from a template. Use an invoice, certificate, quote, purchase order, menu, or social image. Show the template, the input data, and the changed output so the reader can see what is reusable.
- Start from a comparison. Use a dated alternative page and follow its citations to the vendor's source. Recheck the source before publishing because the other product's price and behavior may have changed.
In either case, state the reader's problem, show the evidence, name the limits, and disclose the affiliate link before asking them to try the product.
Show the input, template, and finished output
An editor screenshot proves that an interface exists. A real input and resulting document show whether the workflow solves the reader's problem. Include enough context to reproduce the example without exposing customer data.
- Include the rendered file. Show the invoice, certificate, or report and render a second safe data set when variation is important to the example.
- Pair before with after. Put the captured public page beside its PDF, or the sample form values beside the document they produced.
- Use realistic but synthetic data. Avoid customer information and empty placeholder text that hides how the layout behaves.
- Share the template when appropriate. A cloneable example lets readers inspect the source and test the same workflow in their own account.
Disqualify workflows the platform does not serve
A clear non-fit saves the reader an evaluation and keeps the recommendation accurate. The following jobs should use a different tool or workflow.
- One manual PDF. A word processor or design tool may be simpler when the document will not be generated again.
- Specialist prepress output. Spot colors, press-specific bleed, and other print-production needs belong in a prepress toolchain.
- A finished vertical application. cloudlayer.io supplies document and capture workflows; it does not replace the business application around them.
The stronger fit is repeatable output where source data already exists and a manual transfer, layout, capture, signing, or delivery step creates delay or errors.
Explain the boundary and point to the more suitable category when you know it. That makes the recommendation useful even when the affiliate product is not the answer.
Recommend a repeatable workflow, not a one-time download
Recurring program earnings depend on covered subscription payments. Focus on readers with an ongoing document process and describe the continuing work the platform would perform.
- Name the repeating event. It may be a form submission, scheduled page capture, billing run, order, or application request.
- Show the connection. Explain how input reaches the template and where the completed result goes.
- Include operating needs. Cover error handling, review, storage, and the plan limits that matter to the workflow.
- Avoid retention predictions. Explain ongoing utility without promising how long any referred customer will subscribe.
Link each reader to the relevant product evidence
A specific landing page gives the reader the claims, examples, and limits for that workflow. Choose the audience below to match a problem with the best starting page and demonstration.
They repeat proposal, contract, and report layouts for many clients and need both visual editing and reusable source.
Link them to The designer
Show them
Edit a supported element on the canvas, inspect the source change, and then make a code edit that returns to the canvas.
Keep your introduction focused on the reader's manual step, then let the linked page provide product detail. Recheck both your statement and the destination before publishing.
Choose a format that can demonstrate the workflow
Tutorials
Explain a complete task such as generating invoices from a spreadsheet or building a certificate workflow. Place the disclosed link beside the step where the reader needs the product.
Social posts
Show synthetic input and the document or image it produced. Use a short explanation, a relevant product link, and a visible affiliate disclosure.
Video walkthroughs
Record the template, data, request, and output. Put source links, limitations, and the affiliate disclosure in the description.
Email guides
Walk newsletter readers through one automation and link to the product step being used. Keep the commercial relationship clear near the link.
Guest articles
Write a useful how-to for the publication's audience. Follow its link and disclosure rules rather than hiding the relationship in an author bio.
Product comparisons
Compare products you have tested, cite each vendor's source, record the review date, and explain both matches and differences.
Communities
Answer the question that was asked and mention cloudlayer.io only when it fits. Follow community rules and disclose the affiliate interest.
Podcasts and webinars
Walk through a real automation and put the evidence, disclosed link, and sample resources in the show notes.
Direct recommendations
When the product fits a conversation, send the relevant page and disclose that the tracking link may earn you a share.
Publish an example you can keep accurate
Affiliate content becomes misleading when a price, product limit, or integration changes but the article does not. Build the first version from source links, then give it a simple review routine so the recommendation remains useful after launch.
Record the test setup
Note the template, safe input data, request settings, plan, and date used for the example. Save the resulting file. A reader can then distinguish your tested result from a general statement about every possible document.
Link each changing value
Put a direct source beside prices, allowances, connector actions, SDKs, and program terms. Do not copy a number into an image when a text link can lead the reader to the value that may change.
Explain the operating work
Show how the workflow handles bad input, a failed request, and destination errors. Name any queue, review, storage, or retry logic you added outside cloudlayer.io so the reader does not mistake your application behavior for a platform feature.
Place disclosure with the link
Make the commercial relationship visible before or beside the tracked link, using plain language the audience will understand. Repeat it where a long page, video description, or email can separate the link from the first disclosure.
Recheck comparisons
A dated alternative page is evidence for that review date, not forever. Open the cited vendor page again before publishing and during later updates. Revise or remove a row when the source no longer supports it.
Separate clicks from product fit
Dashboard tracking can show which links and referrals the program attributes. It cannot prove that a tutorial was accurate or that the product suits every reader. Use support questions, corrections, and observed workflow results as separate feedback.
Write from your own test
Describe the steps you performed and the result you inspected. Mark expectations, opinions, and product facts as different things. If you did not test a plan, region, connector action, or file type, link its source instead of implying direct experience.
Keep a correction path open
Give readers a way to report a broken source or a result they cannot reproduce. Check the report against the product and update the article, review date, and sample output when needed. A visible correction is more useful than a stale confident claim.
Add a visible review date to content that contains changing claims. When an example no longer matches the product or terms, update the text and output together. If you cannot reproduce it, remove the claim instead of leaving an old result beside a new affiliate link. Keep the original test notes so a later review can see whether the product changed, the example changed, or the earlier explanation was incomplete. Review the tracked destination too: a correct article can still mislead when its link now opens a different offer, plan table, or product boundary. Record that check beside the content review date.
Affiliate program questions
How much does an affiliate earn?
50% of each eligible subscription payment is credited under the program terms while the referred customer remains subscribed. At a $49 monthly payment, the calculated share is $24.50. Check the affiliate site for attribution, adjustments, and eligibility rules.
When do I get paid?
The program records a monthly payout cadence and a $0 minimum. Configure the available payment details in the affiliate dashboard and review the full terms for processing rules.
Do I need a cloudlayer.io account to be an affiliate?
No. A product account is separate from affiliate enrollment. A free account is useful if you want to test a workflow and show output you created rather than repeat product copy.
What can I promote?
You can explain supported PDF and image generation, page capture, the visual template editor, hosted forms, signing, integrations, and the API. Link to the product page that supports the specific claim and disclose the affiliate relationship.
Review the terms and
apply to the program
Join the cloudlayer.io affiliate program to receive 50% of eligible referred subscription payments, subject to the published program terms.
No credit card required.