> For the complete documentation index, see [llms.txt](https://docs.taskade.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taskade.com/run-your-business-on-genesis/run-your-business/go-live-checklist.md).

# Go-Live Checklist

You described an app, shaped your data, and it works. Before you put it in front of real customers or your team, run this checklist. Each item links to the page that covers it in full — work top to bottom and you'll launch with confidence.

***

### Security

* [ ] **Secrets are vaulted, not hardcoded.** Any API key, token, or password your app uses lives in the secret vault — never pasted into a prompt or page. → [App Secrets](/taskade-genesis/space-apps-guide/app-secrets.md)
* [ ] **The publish guard passed.** Taskade Genesis blocks publishing if it spots a hardcoded credential; resolve any warning before launch. → [App Secrets](/taskade-genesis/space-apps-guide/app-secrets.md)

### Access & data

* [ ] **Login and roles are configured.** The right people can sign in, and each role sees only what it should. → [Add login and roles](/run-your-business-on-genesis/run-your-business/add-login-and-roles.md)
* [ ] **Per-user data isolation is verified.** Sign in as a test client and confirm they can see only their own record — never anyone else's. → [Add login and roles](/run-your-business-on-genesis/run-your-business/add-login-and-roles.md)

### Domain & publishing

* [ ] **Your custom domain is live with HTTPS.** Your app loads at your own address with the padlock showing. → [Put your app on your own domain](/taskade-genesis/space-apps-guide/custom-domains.md)
* [ ] **Visibility and publish strategy are set correctly.** Public, unlisted, or private — match it to who should reach the app. → [Publishing & cloning](/community-and-sharing/community-and-sharing/publish-and-clone.md)

### Cost & reliability

* [ ] **Auto Top-Up is enabled.** A customer-facing agent should never hit an out-of-credits screen mid-session — set a top-up so credits replenish automatically. → [Credits & billing](/help/account-management/credits-and-billing.md)

### Final checks

* [ ] **Test data is purged.** Remove the dummy records you created while building.
* [ ] **A version snapshot is taken**, so you can roll back if a later change misbehaves. → [Publishing & cloning](/community-and-sharing/community-and-sharing/publish-and-clone.md)

***

{% hint style="success" %}
**You're ready to launch.** Every box checked means your app is secure, access-controlled, on your domain, and won't run out of credits in front of a customer.
{% endhint %}

## Next steps

* [From idea to live business — the 5 steps](/run-your-business-on-genesis/run-your-business/from-idea-to-live-business.md)
* [Add login and roles to your app](/run-your-business-on-genesis/run-your-business/add-login-and-roles.md)
* [Put your app on your own domain](/taskade-genesis/space-apps-guide/custom-domains.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 dynamically by asking a question.

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

```
GET https://docs.taskade.com/run-your-business-on-genesis/run-your-business/go-live-checklist.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.