RenderLog

What is RenderLog?

RenderLog is a no-code web testing and visual regression platform. It captures real-browser screenshots, PDFs, and HTML, stores approved baselines, then diffs new runs to surface visual or content changes. Teams catch broken layouts, missing content, and wrong form states before their users ever report them.

Top Features:

• Visual diffing: compares latest captures against approved baselines to highlight meaningful changes.
• No-code testing: content and form-state checks run in a real browser.
• Multi-format output: produces screenshots, PDF, HTML, and Markdown from single runs.
• Flexible execution: run saved checks from UI, API, CI, or schedules.

Use Cases:

• Agency reporting: keep a visual record and show clients exactly what changed.
• Post-release checks: verify pages and flows stay intact after each deploy.
• Content audits: confirm headings, CTAs, and metadata survive CMS and SEO edits.

Who Can Use RenderLog?

• Agencies: monitor client sites and produce weekly visual change reports.
• QA teams: catch layout and form regressions without writing test scripts.
• Developers: wire visual checks into CI pipelines and webhook alerts.

Pricing

• Base (€0.002/run): usage-based capture with screenshots, PDF, HTML, baselines, and webhooks.
• Automation (€59/mo): scheduled checks, 250 suite launches daily, multiple viewports per case.
• High Throughput (€89/mo): handles up to 300 successful runs per minute.

Pros and Cons

Pros:

• Pay per use: failed runs and cached results are never billed.
• No scripting: non-coders can set up checks in a real browser.
• Many outputs: one run yields screenshots, PDF, HTML, and Markdown.

Cons:

• No fixed plan: usage-based billing makes costs harder to predict.
• Add-on modules: automation and retention features cost extra each month.
• Setup effort: defining selectors, viewports, and waits takes initial time.

FAQs:

1) Does it require coding?

No, checks and assertions run in a real browser without writing scripts.

2) How is it billed?

It uses usage-based pricing at €0.002 per successful run, with a €3 minimum.

3) Are failed runs charged?

No, failed runs and cached results without useful output are not billed.

4) What alerts does it support?

It sends Slack, Teams, and webhook alerts when meaningful changes appear.

5) Where can checks run?

Checks run from the UI, API, CI pipelines, or on a schedule.