> For the complete documentation index, see [llms.txt](https://docs.ostara.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ostara.dev/documentation/instances/creating-updating-instances.md).
# Creating / Updating Instances
Instances require an Actuator URL to be created, you can create one or more at the same time. It is not possible to configure authentication settings at the instance level, as the instance always takes its authentication settings from the app.
### Creating an Instance
There are two ways to create a new instance.
The first is by clicking on the `+` sign in the upper left corner, or anywhere on the tree and selecting `Create Instance`. When using this approach, you will also be required to supply an application name, and a new application will be created to house your instance.
The second is by right clicking on an existing app and selecting `Add Instance`, this will automatically pair the new instance with the app upon creation.
In this dialog, you can change the instance's actuator URL, optional alias, and icon.
### Updating an Instance
To update an instance, right click on it and hit `Update`.
In this dialog, you can change the instance's actuator URL, optional alias, and icon.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ostara.dev/documentation/instances/creating-updating-instances.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
