What new customers get
3 months of Pro, free
The full Pro plan: up to 50 monitors, 10 team members, 24 months of metric history and 10 status pages, with server metrics, uptime checks, cron monitoring, vulnerability scanning and alert workflows.
New Fivenines customers
Startup teams that find Fivenines through StartupPerks and whose organization has never paid for it. The offer extends a Fivenines trial, running or already ended, once per company or team.
No card, no automatic charge
Neither the trial nor the offer asks for a payment card. When the 3 months end, choose a plan to keep monitoring (Pro is €49 a month, or €40 a month billed yearly). Nothing is deleted.
Claim it in three steps
We apply the offer by hand after checking that your organization is eligible. A link, a referral code or a visit to this page does not activate it on its own.
Who can claim it
These are all the rules. There is no StartupPerks membership check and no company age, funding stage or location requirement. Our team checks the rules against your Fivenines account before applying the offer.
Frequently asked questions
No. Our team applies it by hand after checking that your organization is eligible. Visiting this page, following a link from StartupPerks or signing up with a referral code only tells us where you came from.
No. There is no membership check and no company age, funding stage or location requirement. The rules are the ones on this page: an organization that has never paid for Fivenines, has not received another partner offer and is not managed by a Fivenines partner, and one partner offer per company or team, whichever partner it came through.
No. Partner offers apply once per organization and do not stack: an organization that has already received one, from StartupPerks or another Fivenines partner, cannot claim a second. A company or team receives one partner offer in all, so another of its organizations cannot claim one either.
No. The 14-day trial and the 3-month offer both run without a card. You add one only if you decide to subscribe.
Monitoring pauses and the account opens on the plan picker until you choose a paid plan. Nothing is deleted, so your servers, dashboards and alert workflows are still there when you subscribe.
Yes, but a subscription starts billing the day you take it and ends the free months that remain. To keep all 3 months, wait for the last days of the trial: the banner then lets you add a card that is first charged when the trial ends.
Any Linux server running a mainstream distribution on amd64 or arm64, such as Ubuntu, Debian, Rocky Linux or AlmaLinux: a VPS, a cloud instance or a dedicated server at any provider, or your own hardware. On Pro, each server, uptime check, cron task, SNMP device and MQTT topic monitor counts as one of your 50 monitors.
No. This offer is for startup teams monitoring their own servers. Hosting providers and agencies who want to resell monitoring to their own customers should read about the Fivenines partner program instead, at fivenines.io/partners.
Something else on your mind? Talk to us →
Monitor a Linux server in four steps
From an empty account to a tested alert. You need SSH access with sudo to a Linux server: a VPS, a cloud instance or a dedicated server at any provider, or your own hardware.
1. Create your account or sign in
Create your account with your email address or with GitHub, or sign in if you already have an account.
With an email signup, confirm your address from the link we send, then sign in. With no server connected yet, Fivenines opens on the Start monitoring screen.
2. Connect your Linux server
Choose Monitor an instance (later on, the Connect button on the Instances page). Give the server a name, for example its hostname, and continue. The wizard then shows the install command for that server. It looks like this:
Paste the command exactly as the wizard shows it, then select Continue. The token at the end belongs to that one server and replaces YOUR_SERVER_TOKEN: keep it private, like a password.
The agent installs as a service running as a dedicated fivenines user. It pushes metrics out over HTTPS, so there is no inbound port to open in the server’s firewall or your provider’s security rules. The agent security page lists what it reads and sends.
3. Check the first metrics
The wizard waits for the agent’s first reports, then shows what it detected on the server. Finish it to open the server’s Overview: CPU usage, memory, filesystem usage and network appear within the first minute, with the CPU, RAM, Network and Storage tabs for detail.
Nothing after a minute? Check what the agent reports on the server with:
4. Configure and test an alert
Every new account starts with an active Instance Status workflow: when a server stops reporting, it opens an incident and emails the members of your account, then emails again when the server is back.
Test it end to end by stopping the agent on the server:
Three to four minutes after the agent’s last report, the incident appears under Incidents and the alert email arrives. Once the agent reports again, the incident closes and a “Back online” email follows.
To be alerted on load too, open Workflows, choose Templates, use CPU Usage Alert (it fires above 90% CPU), then select Activate. For Slack, Microsoft Teams, Telegram, Discord or Pushover alerts next to email (PagerDuty and webhooks come with Business), connect the channel under Integrations.