About Us

Bring document design and code
into one shared workflow

Template updates shouldn't require engineering deployments. cloudlayer.io combines intuitive visual design, editable HTML source, and a high-performance rendering API for automated document workflows.

Start Free See Pricing

Free account, no credit card

The product choices behind the platform

Keep the template portable

Templates use HTML and CSS beneath the visual editor. Edit the same source visually or in code, then export it with the assets needed for use outside the platform.

Reduce workflow handoffs

Separate form, document, screenshot, signing, and delivery tools add credentials and failure points. Keep the steps that belong together in one platform, and integrate externally where the workflow requires it.

Make output template-driven

A saved template and the supplied data define each render. Plan limits state the available concurrency and volume so the workflow can queue and retry around known capacity.

Keep support close to the product

Bring a reproducible template issue or a capacity question to the team. Documentation covers self-service work; plan and agreement terms define response and escalation commitments.

What teams can build with cloudlayer.io

Chromium-based rendering

Build with supported HTML, CSS, JavaScript, fonts, and browser layout features. Validate the template in cloudlayer.io because browser versions and runtime settings can affect output.

Editable starting templates

Clone templates for invoices, certificates, reports, and social images, then adapt their HTML, CSS, assets, and data fields to the job.

Managed asset delivery

Retrieve managed assets and generated documents through the Assets API and CDN-backed delivery, or send output to storage your organization controls.

Free account

Create an account without entering a credit card. Test the product within its free limits, and pick a paid plan when you need more capacity.

Official SDKs

Official SDKs for .NET, F#, Go, Java, JavaScript, PHP, Python, and Ruby. Install from your package manager, or call the REST API directly.

Take the template source with you

Every template on cloudlayer.io is standard HTML and CSS, not a proprietary layout format. You can export clean source code and referenced assets anytime to use in standard browsers or other web editors. 

<section class="invoice">
  <h1>{{ customer.name }}</h1>
  <table class="lines">...</table>
</section>

Readable markup with its stylesheet and data placeholders intact. Another web tool can inspect or edit the source, subject to the features and assets it supports.

Why source format matters

A flattened PDF preserves the finished page but not the reusable design logic. Exported HTML and CSS preserve layout rules, text, and data placeholders in a format common web tools can inspect and edit.

The visual designer and code editor work on the same template source. A round trip keeps visual changes visible in code and supported code changes visible in the designer, subject to the editor's documented HTML support.

What that means in practice

  1. Your templates export as HTML and CSS, and the assets they reference are files you can download.
  2. Generated documents can be delivered to configured storage such as S3 or Google Cloud Storage as they are produced.
  3. Published API versions create a named contract for integrations. Review documented changes and deprecation notices when moving to another version.

An export is a starting point, not a promise that every environment behaves the same. Keep local copies of fonts and assets where licensing allows, note any remote data sources, and render a sample with the target browser or service. That test shows which parts are portable source and which parts depend on the original runtime.

Know where the platform is not a fit

A clear boundary can rule out the wrong architecture before a team invests in it. Check these limits early in the evaluation.

No model chooses each final layout

AI can draft template source and extract structured input. The saved template and input data, not a new model decision, control each production render.

No Office document conversion

There is no Word or Excel conversion route. Use an HTML-first template or choose a tool built to preserve Office document formats.

Usage has stated limits

One finished document is 1 render, and the free account is 50 renders with no card so the limit is visible before you pay. Paid plans start at $9 for 1,000 renders a month.

Recipients are not internal users

An anonymous form respondent or document recipient does not become an internal user. Active organization memberships and render usage are counted separately.

These limits narrow the problem the platform is designed to solve: repeatable output from browser-native templates and structured data. If the source must remain an Office file, keep it in an Office-focused workflow. If every page is a one-off composition, use a design tool. cloudlayer.io fits when one design must produce many documents or images.

Current platform facts

The SDK, connector, action, allowance, and price figures below come from the same site data used by their product pages. They describe the current catalog and plan table.

Running since
2021, on the rendering platform this one grew out of
Official SDKs
8: .NET, F#, Go, Java, JavaScript, PHP, Python, and Ruby, each a public repository
Connectors
732, carrying 727 named actions between them
Free account
50 renders and no card required at sign-up
Entry plan
$9 a month for 1,000 renders
Rendering engine
Chromium-based HTML, CSS, and JavaScript rendering

Catalog counts can grow, while plan amounts can change for new purchases. Follow the product and pricing pages when a number affects a buying decision. This list shows the platform's shape; it does not replace the plan table or an agreement that applies to an account.

Start with reproducible support evidence

Documentation answers common setup questions. Email support covers account, template, integration, and production issues. The selected plan or agreement sets response and escalation commitments.

What tends to be asked

A layout problem is easier to diagnose with the template, a safe sample of its data, the output, and the request settings that produced it. Include the job identifier and expected result when the problem occurs in a render or capture workflow.

For capacity and fit questions, bring the expected monthly volume, peak concurrency, input type, output format, and delivery path. Compare those needs with the pricing table and the named actions available across 732 connectors.

What is written down instead

Documentation covers the API, templating, webhooks, and every one of the 8 SDKs. The template gallery adds working source that can be cloned into an account and adapted, which often explains layout or data binding more clearly than prose alone.

Plan limits are listed on the pricing page. Use those values in capacity planning and confirm contracted terms when the workflow exceeds published tiers.

Remove secrets and personal data before sharing a reproduction unless support needs them and an approved channel is available. A small fixture that still shows the failure is safer to handle, easier to rerun, and clearer about whether the issue belongs to the template, the input, or the delivery path.

Choose managed storage or your own destination

Generated output can use managed storage and the Assets API, return with the request, or go to a configured storage destination. Choose the route that matches the workflow's access, retention, and recovery needs.

Reading them back

Retrieve managed documents through the Assets API and CDN-backed delivery. Follow the documented access rules for each asset URL and application key. A hard-to-guess address is not an access policy.

Keeping your own copy

Delivering to S3 or Google Cloud Storage puts the destination policy, access logs, and lifecycle rules under your cloud account. Test upload failures before depending on that bucket as the only copy. Managed storage is 5 GB on the entry plan and 1 GB on the free plan.

Storage choice does not remove the need for recovery planning. Decide which system holds the authoritative copy, how a failed upload is detected, and who can retry it. Apply lifecycle rules to the destination and verify deletion with a sample object. A bucket you own gives control, but your team must configure that control correctly.

See how render volume changes unit cost

The entry plan has published volume steps. Each step pairs a monthly render allowance with its price, so you can compare the effective cost per completed document as volume grows.

1,000 renders
$9 a month, which is $0.0090 a document
5,000 renders
$29 a month, which is $0.0058 a document
10,000 renders
$49 a month, which is $0.0049 a document

What a render is

One completed document or image uses one render, regardless of the route that triggered it. Page count and file size have separate plan limits, so include document shape as well as monthly count in capacity planning.

What is not metered separately

Trigger route does not create a separate render price. A connector, form submission, scheduled job, and direct API call each consume a render when they produce one completed output.

Where to verify the price

The amounts above are computed from the same plan table used elsewhere on the site. Review the pricing page for included storage, concurrency, page limits, and overage terms before choosing a step.

What happens above the published plans

Requirements beyond published steps are quoted because volume, concurrency, storage, retention, support, and security terms may change together. Bring a representative workload so the quote reflects the actual operating profile.

Estimate cost with completed output, not only incoming requests. Include retries, test runs, seasonal peaks, and any batch that produces more than one document. Compare peak concurrency with the plan as well as the monthly total. A plan can contain enough renders for the month while still needing a queue to absorb a short burst.

Test the estimate with a representative batch before launch.

From the team

Other projects

Other projects built by the same team behind cloudlayer.io

Upstat

Incident response & operational intelligence for DevOps and SREs.

upstat.io

OriJs

NestJS-inspired backend framework for Bun. Provider-based DI, no decorators.

orijs.org

Ori Lang

Expression-based language with automatic reference counting. No GC, no borrow checker.

ori-lang.com

OriTerm

GPU-accelerated Terminal OS written in Rust. Terminal, multiplexer, and session runtime in one.

oriterm.com

WarpKit

State-based routing and navigation framework for Svelte 5.

warpkit.org

Questions about cloudlayer.io

Who builds cloudlayer.io?

cloudlayer.io is built by an independent team focused on document generation, page capture, forms, and the workflows around them. Support requests stay close to the product team, with response terms set by the plan or agreement.

Where are my documents stored?

Generated files can use managed storage and the Assets API, return directly in the response, or go to a configured destination such as S3 or Google Cloud Storage. Choose the delivery and retention path required by the workflow.

Is there a free plan?

Yes. Create an account without a credit card, build a template, and render real documents before you pay for anything. It carries 50 renders a month, and paid plans start at $9 a month for 1,000 renders.

What happens to my templates if I stop paying?

Templates are based on HTML and CSS and can be exported with their referenced assets. That gives you editable source rather than only a flattened output file. Test an exported template in the browser and tooling you plan to use before relying on it as a migration path.

Will the API I integrate against keep working?

Each published API version has a named contract. Integrate against that version, handle documented errors, and review release and deprecation notices before adopting a newer one.

What does cloudlayer.io deliberately not do?

The platform does not convert Word or Excel files and does not use a model to make final layout choices for each render. AI can help draft a template or extract input; the saved template and supplied data control production output.

How many integrations are there?

732 connectors provide 727 automated actions to connect your forms, CRMs, databases, and payment providers. Any other service can connect through signed webhooks or our REST API, with official SDKs available for 8 languages.

Is somebody counted as a user if they only fill in a form?

No. Anonymous form respondents, document recipients, and public viewers do not become internal organization users. Active internal memberships and render usage are separate billing dimensions.

Who is cloudlayer.io not a good fit for?

It is not a fit when Word or Excel conversion is required, when every result needs a model to choose its layout, or when the work is a single hand-placed design with no repeatable data-driven workflow.

How do I get support?

Use the documentation for the API, templates, webhooks, and SDKs, or contact support by email. Response and escalation terms depend on the selected plan or agreement.

Test the workflow with
your own template

Create a free account, build or clone a template, and inspect a real render before choosing a paid plan.

Start Free

No credit card required.