> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/mac-fundamentals/overview/what-is-daylite.md).

# What is Daylite?

Daylite is an all-in-one CRM and productivity app built exclusively for Apple devices. It's made for service-based businesses — people who sell their time and expertise — and it brings your client management, sales, projects, email, calendar, tasks, and notes together in one Apple-native app.

If you want one place where everything about a client lives — who they are, the deal you're working, the project you're delivering, the emails you've traded, and what you need to do next — that's Daylite. Instead of juggling separate tools and chasing scattered details, you get one connected system.

## Daylite is a CRM and a Productivity App in One

Many CRMs focus primarily on managing contacts and sales. Daylite connects that CRM data directly to the projects and day-to-day work those relationships generate.

Everything lives in one database, where related people, companies, opportunities, projects, emails, appointments, tasks, and notes can be linked together.

* **Contacts and Companies** — the people and organizations you work with, and your full history with each
* **Opportunities** — your sales deals, tracked visually through pipelines on the Opportunities Board
* **Projects** — the work you deliver, with linked tasks, timelines, and communication history
* **Calendar, Tasks, and Notes** — the daily tools you use to plan, follow through, and record what matters
* **Email** — your inbox connected directly to your CRM, sales, and projects.

Because sales, delivery, and day-to-day activity share one system, you don't have to manage the client in one tool and the work for that client in another.

## Daylite is a Native Apple App Backed by the Cloud

Daylite is delivered as a subscription. Your data lives in **Daylite Cloud**, and native apps for Mac, iPhone, and iPad sync to it.

Why that matters:

* **Native apps are faster.** feel like they belong on Apple hardware, rather than a website in a browser tab.
* **They keep working offline.** You can work through your opportunities, add notes, and check your calendar with no connection — then everything syncs automatically the moment you're back online.
* **The cloud handles the heavy lifting.** Hosting, syncing across your devices and team, and backups — so there's no server for you to run.

Your subscription covers hosting, sync, backups, and ongoing updates.

## Daylite Connects to Other Tools

Daylite isn't a walled garden. It connects out to the rest of your stack in a few ways:

* **Native integrations** Apple Contacts, and Apple Calendar
* **Automation platforms** such as Zapier and Make, for no-code workflows between Daylite and thousands of other services
* **A REST API** for developers who want to build directly against Daylite


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.daylite.app/help/mac-fundamentals/overview/what-is-daylite.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
