> For the complete documentation index, see [llms.txt](https://docs.mechcloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mechcloud.io/cloud-computing/stateless-iac.md).

# Stateless IaC

Stateless IaC is about managing infrastructure without state files unlike other tools/platforms (e.g. terraform) which heavily rely on state files to manage infrastructure. **MechCloud is the only DevOps platform supports this along with Real-time pricing.**

**Blog post** - <https://dev.to/mechcloud/beyond-terraform-opentofu-a-stateless-iac-with-real-time-pricing-4j2f>

#### **Advantages of Stateless Approach**

* **No state files to manage**\
  Eliminates corruption, drift, and lock issues.
* **Real-time cloud accuracy**\
  Always reflects actual cloud resources.
* **Faster collaboration**\
  Multiple engineers can deploy simultaneously.
* **Instant compatibility with new cloud features**\
  No provider lag.
* **Simpler onboarding**\
  No backend setup, imports, or refresh steps.
* **Lower operational overhead**\
  No backups, migrations, or state storage.
* **More secure**\
  Removes sensitive state file handling and access requirements.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mechcloud.io/cloud-computing/stateless-iac.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.