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

# Publishing and protected output

Publishing turns your original script into the protected outputs used by the loader. Keep your original in your own source control: Vampauth retains the protected bootstrap/payload, not a recoverable copy of that input.

## Publish or replace

Use a nonblank UTF-8 .lua/.txt file or paste original source. The transport limit is 8 MiB; upstream obfuscation limits can be smaller. Publishing a loader/payload uses the owner’s weekly publishing allowance. Check the usage card or GET /api/v2/me for the current effective budget.

An upload/replacement can fail because of input validation, allowance, provider availability, or provider capability. A successful transport test is not proof of successful provider obfuscation. Failed publishing preserves the active output. Supply fresh original input for a rebuild; a protected-content download cannot serve as your original-source backup.

## Changes that do not replace the payload

A display-name-only rename is metadata and spends no publishing credit. URL rotation rebuilds the protected bootstrap and delivery URL while preserving the payload. Moving/reassigning a loader changes which project can use it and must pass both projects’ access rules.

## Updates and running scripts

New executions get the selected published output. Publishing does not replace an already-running script mid-run. Session leases can require fresh authorization after a relevant configuration change.

[Loader setup](/vampauth-docs/development/loader.md) · [Publishing API](/vampauth-docs/api-reference/management/loaders.md)


---

# 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://vampauth.gitbook.io/vampauth-docs/features/publishing.md?ask=<question>&goal=<user_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.