pier.team valid
Pier
A lightweight, self-hosted PaaS written in Rust. Single ~15 MB binary. 20–40 MB RAM at idle. Open-source (AGPL-3.0) alternative to Coolify, Heroku, and Vercel. Deploys Docker containers, Compose stacks and Git repositories with automatic HTTPS, multi-server agents, alerts and notifications, scheduled S3 backups, load balancing with replicas and 35+ one-click templates.
- Authority
- 46 reach 0 · trust 6 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://pier.team/llms.txt
- llms-full.txt
- https://pier.team/llms-full.txt
- Sections
- 6
- Links
- 11
- Size
- 4584 bytes
- Registered
- 2026-04-24
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T13:33:33.441Z
- Last checked
- 2026-10-27T13:33:34.050Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T13:33:33.463Z. Cached copy · Source on pier.team
# Pier
> A lightweight, self-hosted PaaS written in Rust. Single ~15 MB binary. 20–40 MB RAM at idle. Open-source (AGPL-3.0) alternative to Coolify, Heroku, and Vercel. Deploys Docker containers, Compose stacks and Git repositories with automatic HTTPS, multi-server agents, alerts and notifications, scheduled S3 backups, load balancing with replicas and 35+ one-click templates.
Founded: 2026 by Aleksandr Litvinenko.
Language: Rust 2021. Runtime: Tokio. HTTP: Axum. Database: embedded SQLite (WAL).
Repository: https://github.com/joveptesg/pier
Current version: 1.0.0
Install: `curl -fsSL https://pier.team/install | sudo bash`
## Core pages
- [Home](https://pier.team/): what Pier is and why it exists
- [Services catalog](https://pier.team/services): 35+ official one-click templates (databases, dev tools, AI/vector, monitoring, CMS, games, VPN)
- [Features — Alerts & notifications](https://pier.team/features/alerts): 10 preset rules, Telegram/Discord/Slack/email
- [Features — Multi-server](https://pier.team/features/multi-server): lightweight agents, heartbeat, fleet dashboard
- [Features — Backups](https://pier.team/features/backups): scheduled DB & volume backups to S3 / Bunny.net
- [Features — Load balancing](https://pier.team/features/load-balancing): replicas with round-robin / weighted / sticky-cookie
- [Compare](https://pier.team/compare): Pier vs Coolify, Dokploy, Dokku, CapRover and Heroku
- [Changelog](https://pier.team/changelog): every release, reverse-chronological
- [Sponsor](https://pier.team/sponsor): crypto donations — TON, Tron (USDT-TRC20), Solana (SOL + USDT-SPL)
- [Docs](https://pier.team/docs/getting-started/introduction): installation, concepts, applications, security
- [llms-full.txt](https://pier.team/llms-full.txt): full plain-text documentation dump
## Key facts
- Idle RAM: 20–40 MB
- Binary size: ~15 MB
- Minimum VPS: 512 MB RAM, 1 vCPU (a $5/month node is enough)
- License: AGPL-3.0; commercial licenses available on request
- Secrets at rest: AES-256-GCM with a key stored outside the database
- Reverse proxy: Traefik + Let's Encrypt, automatic HTTPS, custom domains, path-based routing
- Database backups: cron-scheduled `pg_dump` / `mysqldump` / `mongodump` / `redis BGSAVE` to any S3-compatible bucket (incl. Bunny.net Storage Zones)
- Multi-server: lightweight Pier agents installed via `curl | sh`, heartbeat, system metrics, location tracking
- Alerts: 10 preset rules (CPU/RAM/disk high, container crashed, deploy/backup failed, agent offline, SSL expiring), routed to Telegram, Discord, Slack and email with cooldowns
- Load balancing: scale services 1→N replicas with round-robin, weighted, or sticky-cookie strategies; replicas distribute across servers
- Authentication: bcrypt password hashing, TOTP 2FA, JWT sessions with revocation, bearer API tokens
- Private registries: per-project and global registry credentials (Docker Hub, GHCR, GitLab CR, AWS ECR, Harbor) — encrypted at rest
- Self-update: atomic binary swap wit
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| dokploy.com | Dokploy | documentation Infrastructure Developer tools | — | 57 | ✓ | ||
| runsite.app | Runsite | interface Data and analytics Infrastructure | — | 45 | ✓ | ✓ | |
| flightcontrol.dev | Flightcontrol (www.flightcontrol.dev) | documentation Infrastructure DevOps and observability | CA | 52 | ✓ | ||
| levelrail.com | Levelrail | documentation Infrastructure DevOps and observability +1 | — | 45 | ✓ | ✓ | |
| easypanel.io | Easypanel | documentation Infrastructure | — | 54 | ✓ | ✓ | |
| ploi.io | Ploi | interface Data and analytics Productivity +2 | NL | 54 | ✓ | ✓ | |
| heroku.com | Heroku: Cloud Application Platform | documentation Infrastructure | US | 65 | ✓ | ||
| relaxdev.ru | RelaxDev | documentation Infrastructure Developer tools | RU | 53 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=pier.team · GET /v1/domain/pier.team · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage pier.team, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for pier.team:
1. POST https://agentwebmap.com/v1/sites/pier.team/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://pier.team/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/pier.team/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/pier.team).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.