![Atrium]()
Atrium
Container
Client portal for agencies and freelancers. Share project progress, files, tasks and invoices through a branded portal. Source: https://github.com/Vibra-Labs/Atrium
Image details
Source details
Configuration
TypeContainerlinuxvibralabs/atrium:latest8080:8080/tcp/var/lib/postgresql/data/app/uploadsBETTER_AUTH_SECRET=''WEB_URL=http://localhost:8080API_URL=http://localhost:8080SECURE_COOKIES=trueDATABASE_URL=STORAGE_PROVIDER=localMAX_FILE_SIZE_MB=50RESEND_API_KEY=EMAIL_FROM=unless-stoppedNotes
Standalone Install
Select an install method, to see config/commands for deploying Atrium
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Atrium, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation, or see Vibra-Labs/Atrium for app-specific guidance.
Atrium
A self-hosted client portal for agencies and freelancers.
What is Atrium?
Atrium replaces shared drives, spreadsheets, and scattered emails with a single branded portal your clients can log into. You own the data and host it yourself.Features
- Project management — Customizable status pipeline per organization
- File sharing — Upload and deliver files via S3, MinIO, Cloudflare R2, or local storage
- White-label branding — Custom colors and logo applied to the client portal
- Role-based access — Owner/admin roles for your team, member role for clients
- Email notifications — Transactional email via Resend
- Built-in database — PostgreSQL included, no separate container needed
Quick Start
The only required variable isBETTER_AUTH_SECRET:docker run -d \
--name atrium \
-p 8080:8080 \
-v atrium-db:/var/lib/postgresql/data \
-v atrium-uploads:/app/uploads \
-e BETTER_AUTH_SECRET=$(openssl rand -base64 32) \
vibralabs/atrium:latestOpen
http://localhost:8080 and create your account.Docker Compose
services:
atrium:
image: vibralabs/atrium:latest
ports:
- "8080:8080"
environment:
BETTER_AUTH_SECRET: "change-me-to-a-random-string-at-least-32-chars"
volumes:
- atrium-db:/var/lib/postgresql/data
- atrium-uploads:/app/uploads
restart: unless-stopped
volumes:
atrium-db:
atrium-uploads:Using an External Database
Disable the built-in PostgreSQL and provide your own connection string:environment:
USE_BUILT_IN_DB: "false"
DATABASE_URL: "postgresql://user:password@your-db-host:5432/atrium"
BETTER_AUTH_SECRET: "your-secret-here"Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
BETTERAUTHSECRET | Yes | — | Random string (min 32 chars) for signing auth tokens |
USEBUILTINDB | No | true | Set to false to use an external database |
DATABASEURL | No | auto | PostgreSQL connection string (required when built-in DB is disabled) |
STORAGEPROVIDER | No | local | File storage: local, s3, minio, or r2 |
S3ENDPOINT | No | — | S3-compatible endpoint URL |
S3REGION | No | us-east-1 | S3 region |
S3BUCKET | No | atrium | S3 bucket name |
S3ACCESSKEY | No | — | S3 access key |
S3SECRETKEY | No | — | S3 secret key |
RESENDAPIKEY | No | — | Resend API key for email |
EMAILFROM | No | [email protected] | Sender address |
MAXFILESIZEMB | No | 50 | Max upload size in MB |
SKIPDBPUSH | No | false | Skip schema sync on startup |
Volumes
| Path | Purpose |
|---|---|
/var/lib/postgresql/data | Built-in PostgreSQL data |
/app/uploads | Uploaded files (when using local storage) |
Links
Serve Atrium on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying atrium.example.com to http://atrium:8080
Add this to your Caddyfile
atrium.example.com {
reverse_proxy http://atrium:8080
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs atrium - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:8080 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :8080 - Stop the other service, or pick a different host port. In
8080:8080only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:8080. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, atrium can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 8080
Image won't pull
Test the pull directly on the host: docker pull vibralabs/atrium:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect atrium --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Required settings are blank
BETTER_AUTH_SECRET, DATABASE_URL, RESEND_API_KEY, EMAIL_FROM have no default value, and atrium may crash or misbehave if left empty.
- Fill them in on the deploy screen before hitting deploy.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on Vibra-Labs/Atrium
- Template not working: Open an issue within the template's repo
- This website not working: Open an issue on lissy93/portainer-templates
A single container
Atrium runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything Atrium needs bundled into one download. This template pulls vibralabs/atrium:latest, which Docker fetches once (about 915 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. Atrium's comes from Docker Hub, published by vibralabs.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 8080:8080 means it's reachable on port 8080 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:8080 in a browser. It opens:
8080:8080, likely the web interface
Volumes
A volume is where Atrium keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/var/lib/postgresql/dataas a volume Docker manages for you/app/uploadsas a volume Docker manages for you
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Atrium takes 9 of them, and 4 need a value before it'll start properly:
BETTER_AUTH_SECRET, needs a value. Auth secret, min 32 chars — generate with: openssl rand -base64 32WEB_URL, defaults tohttp://localhost:8080. Public URL the portal is served from — email invite and reset links are built from thisAPI_URL, defaults tohttp://localhost:8080. Public API URL — same value, the image serves app and API from one originSECURE_COOKIES, defaults totrue. Secure cookies — set to false when serving over plain HTTPDATABASE_URL, needs a value. External PostgreSQL URL (optional, blank uses the built-in database)STORAGE_PROVIDER, defaults tolocal. Storage provider: local, s3, minio or r2MAX_FILE_SIZE_MB, defaults to50. Max upload size in MBRESEND_API_KEY, needs a value. Resend API key (optional, enables invite and reset emails)EMAIL_FROM, needs a value. From address for outgoing email (optional)
Restart policy
The restart policy here is unless-stopped, so Docker restarts Atrium after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Nothing custom is set, so Atrium sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container atrium. That's what you'll spot in the containers list and use in commands like docker logs atrium.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Atrium up. Add the template list to Portainer once, then deploying Atrium is a click rather than a wall of config.