Skip to content
PAUIOps
Open menu

Complete feature catalog

What teams can actually do with PAUIOps.

A practical catalog of the current Manager and Center capabilities—without Kubernetes, SSO, secret-vault, or arbitrary rollback claims.

Capability group 01

Accounts, roles & project access

Give each person the smallest useful operating surface: first by role, then by assigned project.

Session and API authentication

Use a browser session or its paired bearer-token form for API calls without creating separate login identities.

Hardened password handling

bcrypt protects passwords, and supported legacy hashes upgrade after a successful login.

Login throttling

Repeated failures are limited per normalized username and source IP after 10 attempts in 15 minutes; success clears the counter.

Uniform login responses

Known and unknown accounts receive the same error and comparable bcrypt work, reducing enumeration and timing signals.

Optional login verification

Email a single-use six-digit code with expiry, attempt limits, resend limits, and cooldown after password login.

Separate password recovery

An eight-character email code lasts 15 minutes, allows five attempts, and changes nothing until verified.

Recovery abuse controls

Forgot requests return the same generic response and are rate-limited for known and unknown addresses.

Complete revocation

A password reset revokes every user session and token; logout revokes both forms of the same login session.

Secure cookie defaults

HTTP-only, SameSite Strict cookies become Secure under direct TLS or a deliberately trusted HTTPS proxy.

Built-in and custom roles

Start with Administrator, Developer, and Viewer, or define valid role policy through the environment.

Two permission layers

A global role opens product areas while per-project read, write, or none access controls files, Git, and Docker inside a repository.

Account and project administration

Administrators can enable, disable, create, edit, and delete users and projects without removing the final enabled administrator.

Scoped RDS IP allowlisting

Explicitly authorized users can add their validated public IP after password reauthentication, strict request validation, and rate limiting.

Idempotent security-group updates

An already-present AWS ingress rule counts as success instead of creating operator noise.

Capability group 02

Controlled terminal & commands

Make common shell work visible and repeatable while keeping non-admin commands inside approved Git and Docker boundaries.

Live browser terminal

Run streamed command sessions over WebSockets without opening a separate SSH client for routine work.

Role-aware shells

Administrators can receive a full interactive PTY while non-admin commands stay constrained to permitted Git and Docker operations.

Bounded command chains

Non-admin users can combine approved operations with safe top-level && chaining without handing the sequence to an unrestricted shell.

Repository scope

A project selector, active branch display, and local/remote branch discovery keep commands anchored to the intended working tree.

Live project context

CPU and memory visibility beside the terminal helps operators understand the workload while they act.

Repeatable presets

Environment-defined quick commands, history, autocomplete, and suggestions reduce server-specific memorization.

Review-only AI suggestions

An optional Anthropic key can propose Git or Docker commands, but the user must review before execution.

Command guidance

A built-in guide explains Linux, sudo, Git, Docker, and Compose in practical language for newer operators.

Process control

See active background processes and stop work that is no longer needed.

Timeout and concurrency limits

Configurable limits prevent hung or excessive child processes, and cancellation terminates the spawned process group.

Capability group 03

Git & deployment safety

Pause before local work is lost, keep credentials out of URLs, and scope every repository decision to the active project.

Clone and discover projects

Administrators can clone repositories, while startup discovers existing working trees under the managed root without duplicating nested repositories.

Private HTTPS clone

Optional provider credentials are injected through an invocation-scoped authorization header instead of the clone URL or command arguments.

Raw-shell Git authentication

When both credential values are set, startup seeds the runtime user’s .git-credentials at mode 0600 and adds the store helper.

Host-aware credential refresh

A bare PAUIOPS_GIT_HOST selects one URL-encoded entry to replace without duplicating it or damaging entries for other hosts.

Nonfatal credential setup

Home, file, or helper failures warn at startup while the separate application clone path remains available.

Full repository workflow

Status, fetch, pull, push, log, branch, and checkout operations cover routine code delivery.

Fail-closed pull preflight

Modified, staged, untracked, ahead-of-remote, or unverifiable states pause a pull before work can be lost.

Guided pull resolution

Choose commit, push, then pull or stash, pull, then restore when local work needs a safe path forward.

Per-invocation author identity

App-triggered commits use configured name and email without modifying repository or global Git settings.

Path-scoped safe.directory

Each Git call trusts only the active repository and never uses the unsafe wildcard setting.

Secret-reduced runners

PAUIOps-owned Git runners, clone, and helper setup remove PAUIOPS_*, deprecated DOCKER_MGR_*, and SUDO_PASSWORD before spawning Git or hooks.

Non-interactive failure

Terminal prompting is disabled for structured runners so missing credentials fail clearly instead of hanging a request.

Contained clone destinations

Symlink-aware parent checks block escapes, existing targets are rejected, failed partial clones are removed, and errors redact credentials.

Scoped permission recovery

Git metadata errors receive one repository-limited repair attempt and an actionable administrator command.

Capability group 04

Docker & Compose

Operate containers and project stacks from the same project-aware workspace, with explicit confirmation around destructive actions.

Live container inventory

Search container name, image, state, and published ports from one current list.

Container lifecycle

Start, stop, restart, inspect, read logs, or remove containers with confirmation before destructive work.

Assigned Compose projects

The stack selector is derived from repositories the current user is allowed to operate.

Compose operations

Run up, down, status, logs, and configuration validation from a consistent workflow.

Explicit rebuild and volume choices

Image rebuilds are optional and volume deletion is separated behind a clear warning.

Resource visibility

Container and project resource use stays visible next to operational controls.

Startup Docker diagnostics

Manager reports daemon access, Compose plugin availability, and socket-group readiness before users depend on them.

Capability group 05

Images & cleanup

Handle local image work and reclaim space without disguising irreversible operations.

Local image inventory

See what images are present before pulling, building, or removing anything.

Registry pulls

Fetch a named image from its registry through a guided operation.

Server-side builds

Build an image from an approved project context already on the server.

Confirmed image removal

Deletion requires an explicit decision instead of being bundled into a routine action.

Docker diagnostics

Inspect disk usage, engine information, and version from the same interface.

Granular pruning

Prune images, containers, volumes, networks, or all unused resources only after destructive-action confirmation.

Capability group 06

Server health & lifecycle

See health clearly, elevate only exact maintenance commands, and make upgrades recoverable at the Manager binary boundary.

Live system metrics

Monitor CPU, RAM, GPU, disk, dashboard connection status, and streamed output.

Approved maintenance actions

Package list update, package upgrade, reboot, and shutdown use exact sudo allowlisting with confirmation.

Privilege preflight

Startup checks every fixed command with sudo -l without executing package, reboot, or shutdown operations.

Graceful feature degradation

Missing Dashboard privilege or Docker access is reported as a feature warning while safe file and account areas can remain usable.

Startup validation

Project-path access and write checks separate fatal unsafe-root failures from nonfatal feature warnings.

Three probe contracts

/api/health reports detailed state, /api/ready checks startup and database readiness cheaply, and /api/version confirms the running build.

Read-only diagnostics

-doctor provides full evidence while -check offers a concise text or JSON preflight for scripts and CI.

Verified binary upgrade

Manager validates architecture, installs atomically, preserves a backup, restarts, and restores the prior binary if health validation fails.

Graceful draining

SIGTERM and SIGINT stop readiness, drain in-flight HTTP requests within the configured timeout, close the database, and exit.

Capability group 07

Project files & editor

Work inside assigned repositories with layered path and symlink checks around every file operation.

Assigned workspace browsing

Users can open only the repositories assigned to them through an expandable tree and folder view.

Workspace search

Find filenames and file content inside the selected project without searching unrelated server paths.

Permission-aware file actions

Create, rename, and delete files or folders only when the project assignment allows writing.

Multi-file browser editor

Open several source files, track changes, and save one file or all changed files.

Safe previews

Edit and preview Markdown, or inspect HTML through a sandboxed preview.

Workspace context

Project-type detection and an integrated terminal keep code and operations together.

Reloadable assignments

Refresh the workspace after a pull or administrator project reassignment.

Configurable file limits

Bound editable size, uploads, search results, and searched-file size for predictable resource use.

Filesystem containment

Absolute managed-root validation plus symlink-aware checks prevent reads or writes from escaping the selected project.

Capability group 08

Multi-server Center

Use one hosted subscription workspace while keeping every connected Manager server distinct.

Hosted SaaS workspace

Register, subscribe, and open PAUIOps Center while PAUIOps runs and maintains the Center application.

Plan-based server capacity

Choose 2, 5, or Unlimited connected Managers without losing features on smaller plans.

Multi-server registry

Register separate Manager API and WebSocket endpoints and keep each destination server-specific.

Environment and location hierarchy

Organize LIVE, STAGING, regions, and hosts in a searchable server picker.

Registry controls

Test reachability, set a default, enable or disable entries, and control display order.

Per-server sessions

Switching to a Manager without a valid session prompts for sign-in instead of copying credentials across servers.

Consistent operations surface

Overview, Server, Containers, Stacks, Images, Terminal, Files, Processes, Maintenance, and Settings follow the active Manager.

Capability group 09

Integrations & configuration

Configure optional Manager integrations explicitly while Center provides the hosted multi-server workspace.

Cloudflare cache purge

Purge a configured zone through a scoped API token and zone ID.

AWS RDS allowlisting

Authorized users can add a validated public IP to a configured security group.

SMTP delivery

Send login OTP and account-recovery messages through your chosen SMTP service.

SQLite or MySQL

Use SQLite by default or connect Manager user and project data to MySQL.

Environment-defined behavior

Roles, quick commands, origins, cookies, sessions, concurrency, file limits, refresh intervals, and lifecycle timeouts remain operator controlled.

Safe configuration migration

Current PAUIOPS_* values win while deprecated DOCKER_MGR_* keys work only as warned migration fallbacks.

Multi-platform Manager builds

The one-command Manager flow supports systemd on Linux and per-user launchd on macOS; Windows remains a manual binary.

Start with the hosted operations center

Create your account, choose a server plan, and connect your Managers.