Content updates and corrections

Current status

There are no recorded material corrections yet. This page began with the first release of Superluminal’s render-farm and Sulu Market guides on 29 July 2026.

That does not mean every sentence will remain current forever. Blender versions, provider prices, product features, policies, and links change. This page is where we will note changes that could affect a reader’s decision.

What gets listed here

We add an entry when a change affects the meaning of a page, including:

• an incorrect product, provider, pricing, or compatibility detail;
• a calculation or table error;
• a recommendation that changes because an important input changed;
• a broken or replaced source that changes what can be supported;
• a benchmark result that changes after an analysis fix;
• wording that gave a materially broader impression than intended; or
• an update that changes a winner, tradeoff, or buyer decision.

Small spelling, grammar, spacing, and presentation fixes do not need an entry when the meaning stays the same.

Each future entry will name the page, date, previous meaning, corrected information, reason, and effect on any recommendation.

How to report a problem

Send the exact page URL and identify the statement that looks wrong. The most helpful reports also include a current official link, screenshot, invoice, product behavior, reusable scene, output file, log, or calculation that demonstrates the issue.

You do not need to prove that anyone acted in bad faith. A provider can simply tell us that its price, workflow, or policy has changed. A Blender artist can show that a version or add-on behaves differently from the page. A reader can point out that our arithmetic does not add up.

Use Superluminal’s public support contact with the subject Content correction. Do not send credentials, private customer scenes, confidential contracts, or unrestricted invoices in the first message. Describe the material first so a safer review path can be arranged when needed.

What happens next

We first revisit the page and the source or behavior behind the disputed sentence. Depending on the issue, that can mean checking an official provider page, rerunning a calculation, reproducing a product flow, opening the supplied Blender scene, or repeating a render.

If the page is wrong, we update it and add a short entry here. If several pages rely on the same fact, we review those pages too. If the answer is unclear, we narrow the wording or mark the detail as uncertain while checking it.

When a correction changes a comparison, the recommendation changes with it. We do not keep a provider at the top merely because the old wording was convenient.

Fast-changing information

Some information deserves frequent review:

• render-farm prices, credits, trials, and hardware;
• Blender runtimes, engines, and add-on compatibility;
• Sulu Market fees, seller terms, and buyer policies;
• provider storage, retention, support, and security programs; and
• product features described as currently available.

Every comparison shows a check date. Readers making a large purchase should still verify the active provider page and product rate, because a current checkout or contract can supersede an older article.

Corrections to tests and calculations

When a timing, cost, or output comparison changes, the corrected version should retain the same scene and settings where possible. The update should explain whether the problem came from an input, a timer boundary, a missing failure, a formula, a changed provider configuration, or the rendered output itself.

We do not remove a failed run merely because it makes a chart look worse. We also do not keep an invalid result once the flaw is known. The useful outcome is a comparison another Blender artist can understand and repeat.

Why keep this page

Render-farm marketing changes quickly, and technical products are complicated. A visible correction is more trustworthy than quietly replacing the sentence and pretending it was always right.

The rest of the site is written to help artists make practical decisions: prepare a Blender scene, compare farms, understand pricing, choose compatible software, inspect live frames, and recover problems. This page keeps that guidance useful as the underlying products evolve.

For how we compare services, see How we evaluate render farms. For timing and output comparisons, see How we test render farms.