Projects in olic.io act as dedicated containers for your cron job monitors. Whether you are managing multiple clients, distinct server environments, or several different SaaS products, projects keep your data isolated and organized.

Instead of scrolling through a single, chaotic list of mixed tasks, projects give you a clean workspace for each distinct part of your work. This isolation ensures that when you are working on a specific application, you aren’t distracted by the status of another.

Grouping monitors by context

In the early stages of development, a single list of monitors might suffice. But as you scale, keeping track of a production database backup alongside a staging environment health check becomes messy.

We designed projects to solve this. You can think of a project as a “folder” or a group for your monitors. How you organize them is entirely up to you:

• Per Environment: Create one project for “Production” and another for “Staging.”
• Per Client: If you run an agency, create a distinct project for every client.
• Per Server: If you manage heavy infrastructure, group monitors by the specific server they run on.

You can create unlimited projects. Once they are set up, the dashboard navigation allows you to switch between them instantly, giving you total context over the task at hand without the visual clutter.

Handling server timezones

One of the most annoying aspects of monitoring scheduled tasks is dealing with timezones. If your server is in New York (EST) but your monitoring tool assumes UTC, you are going to get false alerts for “missed” jobs simply because of the time difference.

In olic.io, we handle timezones at the project level.

When you create a project, you define the timezone for that specific environment. This means every monitor inside that project automatically respects the server’s local time. You don’t need to do mental math to convert execution times; we sync with your server’s clock to ensure accuracy.

Isolate access for teams and clients

Projects are also the boundary for access control. This is critical for users who work with external partners or freelancers.

You likely don’t want a freelance developer to have access to your entire business dashboard, or Client A to see the error logs of Client B. Because members are added to specific projects, you can granularly control who sees what.

Projects allow for easy collaboration by letting you invite relevant team members or partners only to the workspace they need. They get the data they need to fix issues, and your other data remains private.

Getting started with a new project

Setting up a new project is designed to be lightweight. We hate bloat, so we kept the configuration strictly to the essentials.

To start a new project, you only need two things:

1. A Name: To identify the project in your dashboard.
2. A Timezone: To match the server location where these jobs are running.

Once created, you can immediately start adding monitors and notification teams to that specific project.

If you are currently running all your monitors in one default view, try spinning up a new project for your staging environment today. You will notice immediately how much faster it is to identify issues when your dashboard is clutter-free.