# Is Uvilno's automatic repair unlimited?

Canonical: https://uvilno.com/answers/is-automatic-repair-always-free-and-unlimited
Updated: 2026-10-27

Uvilno's platform-funded repair is limited to native static-project faults reproduced by server-side browser checks. It has per-version, project and owner admission limits and a bounded free-model response. Ordinary edits and broader repairs remain metered, and failed recovery preserves the saved version rather than claiming success.

The live iframe can report a critical observation, but its message cannot authorize arbitrary free coding. The server independently reproduces the fault, selects a small affected file set, validates complete replacements and checks the rendered result before publication.

A new feature, redesign or general question is not a runtime repair. Next.js verification and normal generation keep their own contracts. If automatic recovery cannot verify a safe result, use the saved version and a precise bug report; no finite system can promise every future error will disappear.

## What to verify

| Check | Published behavior | Verification |
| --- | --- | --- |
| Eligibility | The bounded path covers native static runtime faults. | Confirm the issue is reproduced in isolation. |
| Funding | An eligible repair adds no customer model-usage charge. | Distinguish it from a requested feature edit. |
| Outcome | Publication requires checks; failure preserves the prior version. | Review the actual saved version and runtime state. |

## Steps

1. Describe the failing route and action.
2. Keep the previous verified version available.
3. Confirm a repair passed rather than trusting a loading label.

## Editable starting brief

Inspect a reproducible runtime failure on the current saved route. Reproduce the issue before attempting a bounded correction, retain the previous version, preserve unaffected files and only announce success after verification. If the issue is outside the supported automatic repair scope, explain the next actionable step without claiming an untested fix.

## Sources

- [Uvilno public SDK documentation](https://uvilno.com/docs)