# Deploying an Axon in Turium

After you finish designing and debugging an axon and are satisfied with the data you see in Preview, you are ready to deploy the axon.

{% hint style="info" %}
Note: A deployed axon name must be unique in the namespace. You might be prompted to enter a unique name.
{% endhint %}

Deploying converts the axon into an immutable entity, which is not versioned.

After deployment, the axon can be either run manually using the Run button, scheduled on a time basis using the Schedule button, or triggered based on the completion of another axon using Incoming Triggers.

The Genesis saves a run history of the axon each time it runs. You can toggle between different runtime versions of the axon:

When you deploy the axon, the Genesis creates the workflow and corresponding Spark jobs in the background.

Once you deploy an axon, you cannot edit it. You can duplicate it or export it and then import it into the Genesis.

After you deploy an axon, you can configure runtime arguments if the axon includes nodes.

***

<br>


---

# Agent Instructions: 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.turium.ai/home/algoreus/turium-connector-documentation/turium-fabriq-overview/how-to-guides/axons-pipeline-user-guide/deploying-an-axon-in-turium.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.