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

# Telepúrte

> Linux Infrastructure Management: Node Park, SSH and Files, Access, Automation, Surveillance and Operation.

Telepúrte is a stand-alone Linux infrastructure management tool, and in one panel you can build a fleet of servers, organize team and contractor access, work in the terminal and with files, run Bash scripts and Ansible playbooks, manage services, and disassemble session records and audit activities.

Telepúrte works for free. It can be used independently or linked to Axottle for login, synchronization of users, projects and nodes. Axottle is not required for autonomous operation.

## Capacity by task

| Problem | What is in Telepúrte | Guide |
| - | - | - |
| Collect | Infrastructure Connect Linux servers one by one and a bundle, import Axottle, search, tags, groups and locations | [Park nod](https://docs.axottle.com/en/telepurte/nodes.md) |
| Deal with the car. | Metrics of CPU, memory and disk, processes, systemd services, log and limitations | [Page of the node](https://docs.axottle.com/en/telepurte/node-workspace.md) |
| Work with hands | Web SSH tabs, ordinary SSH client through the bastion, transitions from the terminal to files | [Terminal and SSH](https://docs.axottle.com/en/telepurte/terminal.md) |
| Modify | Web SFTP files, configuration search and verification editor, file rights, media preview and PDF | [Files and editor](https://docs.axottle.com/en/telepurte/files.md) |
| Organize the access of the | team Users, MFA, inheritance roles, grants, personal Linux accounts, groups and sudo | [Users](https://docs.axottle.com/en/telepurte/users.md), [roli](https://docs.axottle.com/en/telepurte/roles.md) |
| Introduce contractor at time | Guest link, separate SSH password, selected nodes, term, visits and recall | [Time access ](https://docs.axottle.com/en/telepurte/temporary-access.md) |
| Repeat operations | Playbook versions, Bash and local Ansible, files and environment variables, typed actions | [Playbooks](https://docs.axottle.com/en/telepurte/playbooks.md), [scripts](https://docs.axottle.com/en/telepurte/scripts.md) |
| Manage the launch on the | Park Target check, results of each step and nodes, stop the remaining work, phased rollout through the API | [Tasks](https://docs.axottle.com/en/telepurte/jobs.md) |
| Do work regularly | Days of the week, time, time zone, pass processing, fixed goals and history | [Schedules](https://docs.axottle.com/en/telepurte/schedules.md) |
| Control configurations | Approved files, application and verification of content and rights, history of discrepancies | [Configurations](https://docs.axottle.com/en/telepurte/configurations.md) |
| Investigate the actions of | Audit, SSH/SFTP history, terminal playback and observation of the active session of | [Sessions and audit](https://docs.axottle.com/en/telepurte/audit.md) |
| Connect an external assistant | MCP with OAuth and separate read permissions, diagnostics and commands | [MCP](https://docs.axottle.com/en/telepurte/mcp.md) |

## How the work is done

**Panel** stores users, rights, park settings, playbooks and history. **Bastion**Bastion serves SSH and Web SFTP connections. **Agent on the node** performs supported operations, reports status and can provide a tunnel to SSH. These components solve different tasks: a live agent does not mean that the user can open the terminal, and the available terminal does not issue rights to mass tasks.

```mermaid theme={null}
flowchart LR
    U[Пользователь] --> P[Панель Telepúrte]
    U --> B[Бастион SSH / Web SSH / SFTP]
    P --> B
    B --> N[Linux-ноды]
    P <--> A[Агенты на нодах]
    A --> N
    X[Axottle — по желанию] --> P
```

First, the node appears in the directory, then its SSH identity and connectivity are confirmed, then the specific user is assigned access and system login, and the agent and its local permissions are further checked before automation.

## Three working routes

### Daily operation

Find a node by name, IP, project or tag → open metrics and services → go to the terminal or editor → check the result → if necessary, go back to the session recording. An example of a diagnostic service is available on the [page of the node](https://docs.axottle.com/en/telepurte/node-workspace.md).

### Team work

Create users → define roles for the right groups of nodes → select personal Linux accounts and necessary groups → check access under a regular account. For a contractor who does not need a panel, create a separate [temporary access](https://docs.axottle.com/en/telepurte/temporary-access.md).

### Repeated changes

Prepare a script or set of actions → save the playbook version → execute on a test node → check the output and actual state → select work goals → run manually or on schedule.

## Beginning of work

> [card] [Installation](https://docs.axottle.com/en/telepurte/installation.md)
>
> Self-installation or Axottle master, first owner and HTTPS.

> [card] [First working scenario](https://docs.axottle.com/en/telepurte/quickstart.md)
>
> From node connection to terminal, diagnostics and audit verification.

> [card] [Link to Axottle](https://docs.axottle.com/en/telepurte/access.md)
>
> SSO, import, project, agent training and revocation of access.

> [card] [If something doesn't work.](https://docs.axottle.com/en/telepurte/troubleshooting.md)
>
> How to Distinguish Entry Problem, SSH, Agent, Rights, or Task.

## Verification

Readiness is assessed throughout the work path: user input, visibility of the desired node, SSH connection, file operation in the authorized directory and the result of a separate task of the agent. Section **Overview** helps to see the state of the components; to verify the rights, use a regular user.

## Rollback

Access is revoked through roles, grants, or disabling the user; tasks are stopped separately; changes already made require reverse operation. Before disabling the entire installation, save [a backup copy of](https://docs.axottle.com/en/telepurte/backups.md) and independent administrative access to the servers.

Feature availability depends on the panel version, bastions, and agents; older builds may not contain the features described.


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