Run Metribay yourself
Self-hosted, Лично издание, е Metribay на твой сървър. Безплатно, open source, Apache-2.0.
Is it right for you?
Section titled “Is it right for you?”| Self-hosted | Metribay Cloud | |
|---|---|---|
| Cost | Free | See Plans and billing |
| People | One person | Teams with roles |
| Workspaces | One, in the background | Up to 5 |
| Projects and data sources | No limit | 10 and 50 active |
| Integrations | All seven | All seven |
| Updates, backups, uptime | You | Us |
| Google sign-in button | Your own Google app | Provided when available |
Self-hosting ако можеш PHP app и own hardware. Cloud ако не искаш server ops или team.
Requirements
Section titled “Requirements”- PHP 8.5+ with cURL, OpenSSL, PDO (SQLite or PostgreSQL), intl, mbstring
- Composer 2
- SQLite or PostgreSQL
- systemd/Supervisor + cron for background processes
- Node 24 only to rebuild frontend; release includes assets
Install
Section titled “Install”-
From repository root, then app:
Terminal window ./scripts/setup.shcd standalone -
Create account (password asked privately):
Terminal window -
Web server. Quick local:
Terminal window php artisan serve --host=127.0.0.1 --port=8000Production:
standalone/publicover HTTPS. -
Queue worker + scheduler:
Terminal window php artisan queue:work --timeout=900php artisan schedule:workProduction: process manager + cron
php artisan schedule:runevery minute.
Sign in with install email/password. Registration off — one account.
How collection runs
Section titled “How collection runs”Scheduler: collection every 4h, uptime hourly, full history weekly — like Cloud. Needs queue worker + scheduler.
Manual sync:
php artisan metribay:sync # queue every active data sourcephp artisan metribay:sync --kind=github # only one providerphp artisan metribay:sync --except=uptimerobotphp artisan metribay:sync --source=12 # one data source by IDphp artisan metribay:sync --full # reread the whole history windowphp artisan metribay:sync --inline # run now, without the queueConnecting providers
Section titled “Connecting providers”Own credentials per integration guides. Nothing through Metribay servers.
Свържи Google for Analytics/Search Console — own OAuth client:
-
Google Cloud: enable Analytics Admin, Analytics Data, Search Console APIs.
-
OAuth Web application, redirect:
https://metribay.example.com/integrations/google/callback -
.env:METRIBAY_GOOGLE_CLIENT_ID=your-client-idMETRIBAY_GOOGLE_CLIENT_SECRET=your-client-secretMETRIBAY_GOOGLE_REDIRECT_URI=https://metribay.example.com/integrations/google/callback
Google app in testing: sign-ins expire after 7 days. Service accounts don’t.
Production checklist
Section titled “Production checklist”-
HTTPS,
APP_ENV=production,APP_DEBUG=false -
.env, DB, backups outside public web -
Never cache signed-in pages at CDN/proxy
-
After update:
Terminal window php artisan migrate --forcephp artisan vendor:publish --tag=metribay-assets --forcephp artisan queue:restart -
Mail transport for password reset
Backups
Section titled “Backups”- Database. SQLite online backup; PostgreSQL
pg_dump. APP_KEY. Encrypts credentials — without key, DB backup useless. Don’t change key without re-encrypt plan.
Test restore. Configuration export helps but not full backup — no history/credentials.
Moving to Metribay Cloud
Section titled “Moving to Metribay Cloud”Export configuration, Cloud sign up, connected accounts same names, import. Cloud re-collects history within each history window.