Introduction

Nubes brings your application and its infrastructure into the same workflow. Describe what your project needs in code, review the changes, and decide when to put them live.

Keep the tools you already enjoy. Your agent can help with the infrastructure, just as it helps with the rest of your codebase.

A familiar way to build

Start with a project, not a dashboard. The infrastructure lives alongside your application in a small HCL file: nubes.hcl.

You can keep it at the project root or in a folder such as .ai/. The folder is your choice, not a requirement.

That file describes your app and the resources it needs. It belongs in version control, so changes can be read, discussed, and reviewed together.

Made for your agent

An agent should be able to understand how your application is put together without guessing at settings hidden in a control panel.

With Nubes, the workflow is explicit:

1. Inspect the project and understand how it runs.
2. Describe the app and only the resources it needs.
3. Plan the changes and explain them.
4. Deploy after you approve.

The agent helps you move faster. You stay in control of what goes live.

Start small

An app does not need a database just because a template includes one. Add resources when your project needs them, and keep the infrastructure easy to understand.

The same idea applies to the documentation: start with your first project, then explore apps and secrets as you need them.