OneUptime is an open-source complete observability platform.
OneUptime monitors your website, dashboards, API's, and more and alerts your team when downtime happens. We also give you a Status Page which keeps your customers looped in and improves transparency.
OneUptime does:
- Uptime Monitoring, replaces tools like Pingdom
- Status Page, replaces tools like StatusPage.io
- Incident Management, replaces tools like Incident.io
- On-call rotation and alerts, replaces tools like PagerDuty
- Tests, replaces tools like Postman (Coming soon)
- Security, replaces tools like Snyk (Coming soon)
- Logs Management, replaces tools like Loggly (Coming soon)
- Performance Monitoring, replaces tools like NewRelic (Coming soon)
- Error Tracking, replaces tools like Sentry (Coming soon)
All under one platform.
The fastest and most reliable way to get started with OneUptime is signing up for free to OneUptime Cloud. By using the hosted cloud service, you also support by funding OneUptime open source development.
Deploy a single-server instance with docker compose on Debian / Ubuntu (we only support Debian / Ubuntu as of today). We recommend OneUptime on 16 GB / 8 Core Ubuntu Server. However you can run an instance on a much smaller server.
To install:
git checkout release # Please make sure you're on release branch.
cp config.example.env config.env
# IMPORTANT: Edit config.env file. Please make sure you have random secrets.
source config.env
docker-compose up -d
To update:
git checkout release # Please make sure you're on release branch.
git pull
docker-compose pull # Fetch new images.
docker-compose up -d
OneUptime should run at: http://localhost. You need to register a new account for your instance to start using it.
Our mission is to reduce downtime and increase the number of successful products in the world. To do that, we build a platform that help you understand causes of the downtime, incidents and help reduce toil. Our product is open-source, free and available for everyone to use.
We <3 contributions big and small. In priority order (although everything is appreciated) with the most helpful first:
- Give us feedback in our Customer Slack community
- Talk to developers in our Developer Slack community
- Write tests for some of our codebase. See issues here
- Work on any issue you like. See issues here
- Open new issues and create new feature requests that you would like to see. Open issues here
If you like the project, please consider a small donation. Every single dollar will be used to ship new features or maintain existing ones. 100% of the work we do is open-source. Please donate here