> ## Documentation Index
> Fetch the complete documentation index at: https://resources.athenaintel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Security and operations for apps hosted on Athena

> How Athena secures and runs the apps you host on it: private by default, company sign-in, recorded releases, your choice of cloud, managed databases with point-in-time recovery, and audit exports. Use it to prepare a security review.

> Apps you host on Athena start private, sign people in with your company login, and keep a record of every release. They run wherever Athena runs, including your own cloud or your own servers, and Athena can rebuild any saved version on demand. This page walks through each area a security review covers. For each one it says what Athena handles, what your team adds, and what to confirm with your admin.

## At a glance

| Topic | What Athena does | What you set up |
| - | - | - |
| Who can open the app | Private by default, with Athena sign-in or the client's company login | Who has access, and your own gateway if policy requires a firewall |
| Releases | Publishes from a chat, an uploaded build, or an optional GitHub connection; records every version and can roll back to any of them | Who has edit access, and required reviewers and checks in GitHub if you connect it |
| Where it runs | Athena's cloud, your cloud, your own servers, or offline | Your choice, agreed with Athena |
| Reaching other systems | Admin limits on outside addresses for Automations and, where supported, Computers | Routes to private systems, planned with your admin |
| Data | If the app uses an Athena database: managed Postgres with seven days of history, copies, and restore | If the app uses your own database: its backups, encryption and access rules. Either way, a separate login for each app |
| Traffic | HTTPS with managed certificates | A check of the live site's settings |
| Logs and records | Keeps release and health-check output, and lets admins export audit records | Your monitoring tool, and a schedule for audit exports |
| Retention | Legal holds and retention rules on workspaces and assets | Rules inside the app for keeping and deleting records |
| Running and recovery | Rebuilds any saved version, and sleep can be turned off | Your own recovery plan, tested once |
| Starting point | Lets admins publish approved Computer environments | Your approved environment |

## Who can open the app?

Every Application is private when you publish it. Only people who are signed in and have access can open it. Making an app public takes edit access plus admin rights, or an admin's permission. If your workspace requires a security scan, an admin clears or accepts its findings before the app goes public.

![Three ways into your app, which is private unless you share it. Your staff sign in with your company login. Your client's staff sign in with their own company login and reach this app only. The public get in only if an admin allows it, after any required security scan. To filter by IP address, put your own gateway in front.](https://mintcdn.com/athenaintelligence-e46bc9d3/U4e92C1IcbO5Ytjz/images/build-guides/security-review-answers-2.webp?fit=max\&auto=format\&n=U4e92C1IcbO5Ytjz\&q=85\&s=f07affa171f9d8da5547d1bd2c640ddf)

Your staff sign in with your company's single sign-on (SAML or OIDC), and SCIM can add and remove users for you as people join and leave. See [SSO](https://resources.athenaintel.com/docs/getting-started/sso.md). A client's staff can sign in with their own company login and reach only that app. See [Build for a client](https://resources.athenaintel.com/docs/build-guides/forward-deployed-teams.md).

Sign-in is the main control. If your policy also calls for filtering by IP address or a web application firewall, send traffic through your own gateway in front of the app's web address. A gateway only filters traffic that passes through it, and the app's Athena web address still reaches the app directly. Have Athena build the app to refuse any request that lacks a secret header your gateway adds, so traffic cannot go around the gateway. Leave the health check path out of that rule, because Athena calls it directly to decide whether a new version can go live.

For public apps, Athena blocks a list of web addresses that attackers often probe. Ask Athena to write per-user request limits into the app as it builds, as [the build standard](https://resources.athenaintel.com/docs/build-guides/build-standard.md) describes.

## How are releases approved and recorded?

An Application can be published several ways. Ask Athena to release it from a chat, upload a packaged build in the app's **Deployment** tab or through the API, or connect it to a GitHub repository. Git is optional. Every path saves a new version, builds it and checks that it is healthy before it goes live. You can also stage a version, check it in preview, and promote it later.

Inside Athena, anyone with edit access to the app can publish, and Athena does not ask for a second approver. Give edit access only to the people who own releases. If your review needs a second person to approve each release, connect the app to GitHub and require the review there.

Athena keeps a record of every version: who made it and when, its size, and a fingerprint of its contents (a SHA-256 hash). It can also record a release note and the version it came from. Each publish records who published it and when.

### If you connect GitHub

Only the app's owner can connect a repository, and the connection supports GitHub and GitHub Enterprise. Require a review before anything merges into the connected branch, and make your tests required checks so only tested code reaches it.

![Releasing from GitHub. A pull request gets its own preview with no real Secrets. Review and tests are required in GitHub. The release branch is updated when merged. Athena publishes the new version: right away if it came from someone who can edit or an allowed bot, and after the owner approves if it came from anyone else. Every version keeps a record of who made it and when, its size, a fingerprint of the files, the repository, branch and commit, and what started the build. Footer: make your tests required checks in GitHub.](https://mintcdn.com/athenaintelligence-e46bc9d3/U4e92C1IcbO5Ytjz/images/build-guides/security-review-answers-3.webp?fit=max\&auto=format\&n=U4e92C1IcbO5Ytjz\&q=85\&s=39b92c258fab23719f79dae1b9f82237)

A push to the connected branch publishes a new version once its build and health check pass. A push from a workspace member with edit access whose GitHub account is linked, or from a bot you have allowed, goes ahead on its own. A push from anyone else waits for the owner's approval. If you release through your own pipeline, have it push to the connected branch and add its bot to the app's allowed bots.

A pull request into the connected branch can get its own preview. A preview never touches the live app and never receives the app's real Secrets. Pull requests from forks don't get previews. To keep pushes away from the live app entirely, turn off **Production deploys** in the app's Git connection.

For versions built from GitHub, Athena also records the repository, branch, commit, who pushed it and what started the build.

If your review asks for signed packages or a software bill of materials (a list of every library the app uses), produce them in your own pipeline before the build reaches Athena.

## Where does it run, and what can it reach?

You choose where Athena runs: Athena's cloud, your own AWS (including GovCloud), Azure or Google Cloud account, your own servers, or fully offline. Hosted apps and their databases run wherever Athena runs, so when Athena is in your cloud, your apps and their data stay there too. See [deployment options](https://athenaintel.com/deployment-options/).

![Athena can run in Athena's cloud, your cloud on AWS, GovCloud, Azure or Google Cloud, your own servers, or fully offline, and your apps and their data run wherever Athena runs. When an Automation calls a website, admins can limit where. A call that sends a password or key goes to approved addresses only. In a Computer's Network tab, admins choose where it can connect. Footer: plan access to your private network with your admin.](https://mintcdn.com/athenaintelligence-e46bc9d3/U4e92C1IcbO5Ytjz/images/build-guides/security-review-answers-4.webp?fit=max\&auto=format\&n=U4e92C1IcbO5Ytjz\&q=85\&s=6c9ef5f055a73f5d43a52d409023b11e)

Admins can limit which outside addresses an Automation's web requests may call, and a request that carries a Secret, such as an API key, can only go to an approved address. Where your setup supports it, an admin can also choose which outside addresses a Computer can reach, in its **Network** tab. The change takes effect the next time the Computer wakes up.

Reaching systems on your private network depends on how your Athena installation is networked. Plan those routes with your admin.

## How is the data protected?

An app can keep its data in an Athena database or in a database you already run. The answers differ.

If the app connects to your own database, that database's backups, encryption, access rules and audit logs apply, and Athena does not change them. Store its connection details as Secrets and give the app a login that reaches only what it needs.

The rest of this section covers Athena databases. Each one is Postgres, run by Athena inside your Athena setup. If Athena runs in your cloud, the database does too.

An Athena database keeps a continuous history, seven days by default. You can make a copy of it as it was at any point in that window, or restore the main database in place. A restore disconnects anyone connected and keeps the data it replaced as a protected copy. Copies and restore are marked Experimental.

![Seven days of database history, kept all the time. You can make a copy from any point, or roll the database back and keep the replaced data as a copy. Both are marked Experimental. Below, each app gets its own database login that can only reach that app's tables. Footer: check encryption with your admin.](https://mintcdn.com/athenaintelligence-e46bc9d3/U4e92C1IcbO5Ytjz/images/build-guides/security-review-answers-5.webp?fit=max\&auto=format\&n=U4e92C1IcbO5Ytjz\&q=85\&s=103161fb29cf09fa823a6575b0e9f30f)

Only people with edit access can see the database's connection details. Give each app its own database login that reaches only that app's tables. See [Databases](https://resources.athenaintel.com/docs/pillars/applications/databases.md). If you ever need to change the main password, Athena staff can do it on request, and the old connection details stop working.

Encryption of stored data and of database connections is set per installation. Confirm both with your admin before you store sensitive data.

To track who changed which record, ask Athena to add `updated_by` and `updated_at` columns, or a table that records each change. The database's query history shows recent activity and is not meant as a full change log.

## How is traffic encrypted?

Every hosted app is served over HTTPS. Athena manages the certificates for its own app links. If you use your own web address, your setup decides its certificate and whether plain HTTP is redirected to HTTPS.

![A browser connects over HTTPS to Athena's front door, where Athena manages the certificates, and the front door passes the request to your app. With your own web address, your setup provides the certificate and the redirect to HTTPS. Footer: check the live site's security settings.](https://mintcdn.com/athenaintelligence-e46bc9d3/U4e92C1IcbO5Ytjz/images/build-guides/security-review-answers-6.webp?fit=max\&auto=format\&n=U4e92C1IcbO5Ytjz\&q=85\&s=edc6eb80a964e79cb031980c486dad43)

Before the review, check the live site's settings directly, including its TLS version and whether it sends a strict-HTTPS (HSTS) header. If you need a content security policy, add it in a `<meta http-equiv="Content-Security-Policy">` tag in the page and confirm in the browser that it works.

## Where do logs go?

Admins can export asset history and admin events as CSV or JSON at any time. Schedule a regular export into your security monitoring system (SIEM). See [Audit records](https://resources.athenaintel.com/docs/getting-started/audit-records.md).

![Where logs go. Audit records, meaning who changed what and admin actions, are exported on a schedule to your security monitoring. App logs, meaning what your app writes while it runs, are sent by the app itself to your monitoring tool. Release logs from builds and health checks are kept in Athena.](https://mintcdn.com/athenaintelligence-e46bc9d3/U4e92C1IcbO5Ytjz/images/build-guides/security-review-answers-7.webp?fit=max\&auto=format\&n=U4e92C1IcbO5Ytjz\&q=85\&s=98bc8261fd5a185cf2a908005f2773ba)

Athena keeps the build and health-check output for every release. For what the app does while it runs, ask Athena to add OpenTelemetry or your monitoring vendor's library, and the app sends its logs and performance data straight to the tool your team already watches.

## Do legal hold and retention cover app data?

Workspace owners can place legal holds and set retention rules on workspaces and assets. Held items are kept, and Athena records who placed or released each hold. See [Legal holds and retention](https://resources.athenaintel.com/docs/getting-started/legal-holds-and-retention.md).

![Two kinds of record. Workspaces, files and other assets: Athena's legal holds and retention rules keep them, with a record of who placed each hold. The app's own database: the app's own rules decide what to keep, delete and check, and Athena builds those rules into the app. Footer: check with your admin that holds are switched on.](https://mintcdn.com/athenaintelligence-e46bc9d3/U4e92C1IcbO5Ytjz/images/build-guides/security-review-answers-8.webp?fit=max\&auto=format\&n=U4e92C1IcbO5Ytjz\&q=85\&s=63580a94f146df597ae85f46e24077e8)

Records inside an app's own database follow the app's rules, and a hold does not freeze them. Ask Athena to build your rules for keeping and deleting records, and any checks for sensitive data, into the app. Confirm with your admin that holds are enforced in your setup.

## How does the app run, and how does recovery work?

Each Application runs as a single copy, and an admin can move it to a bigger machine when it needs more room. By default, a live app sleeps after 30 minutes without traffic, a preview after 10 and a Computer after 60. Set any of them to never sleep and it stays ready.

![An app goes to sleep when no one uses it: after 30 minutes for a live app, 10 for a preview and 60 for a Computer, and each can stay awake all the time. Every version is saved, v1 to v4 with v4 live, and you can roll back to an earlier version. Files the app saves to its own disk are not saved with the version, so keep data in the database.](https://mintcdn.com/athenaintelligence-e46bc9d3/U4e92C1IcbO5Ytjz/images/build-guides/security-review-answers-9.webp?fit=max\&auto=format\&n=U4e92C1IcbO5Ytjz\&q=85\&s=c3b7d3980f415eede6c5d29c8b541fce)

Every version is saved as a package that Athena can rebuild at any time, so rolling back means rebuilding an earlier one. Keep anything that matters in the database, because files the app writes to its own disk are not part of the package. By default a build can take up to 15 minutes and the finished package can be up to 200 MiB. Your setup may use different limits.

Hosted apps don't come with a set uptime or recovery time. If your review asks for one, write your own recovery plan from the steps above, test it once with a real restore, and talk to your Athena contact before you commit to a number.

## Can builders start from an approved setup?

Yes, where environments are turned on. An admin builds and publishes an approved environment, and builders create Computers from it with view access. Everyone starts with the same approved tools and settings, and with [the build standard](https://resources.athenaintel.com/docs/build-guides/build-standard.md) already in place.

![An admin builds and shares an approved setup with approved tools, settings and the build standard. Your team starts Computers from it. Footer: only admins can create a setup.](https://mintcdn.com/athenaintelligence-e46bc9d3/U4e92C1IcbO5Ytjz/images/build-guides/security-review-answers-10.webp?fit=max\&auto=format\&n=U4e92C1IcbO5Ytjz\&q=85\&s=92d4c359fb4d3d2261d4d592e1a4acc2)

## What to plan for

* Six settings vary by installation: sleep time, database history, encryption, environments, legal hold enforcement and the security scan. Get your values from your admin and put them in the review.
* If a gateway sits in front of your web address, test sign-in and live updates through it, and check that the app refuses a request sent straight to its Athena web address.
* Practice recovery once before you need it. Restore a database copy and republish an older version.

## Questions teams ask

> [accordion] Does this apply to AOPs and Automations?
>
> No. Athena runs AOPs (saved AI procedures) and Automations itself, with their own access, approvals, budgets and run history. This page covers apps hosted as Applications or on Computers.

> [accordion] Who can make an app public?
>
> Someone with edit access who is an Athena admin, or whom an admin has allowed to make apps public.

> [accordion] Can outside people sign in without an Athena seat?
>
> Yes. Connect the Application to their company login. They sign in with their own accounts and reach only that app.

> [accordion] Where are the rules Athena follows when it builds?
>
> In [the build standard](https://resources.athenaintel.com/docs/build-guides/build-standard.md).

> [card] [See it work](https://athenaintel.com/demo/)
>
> Thirty minutes, your workflow, and you leave with the work product.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.