# The Temporal Grid

Every Cronofy capability is built on the Temporal Grid. Your application
connects to it once, and each capability you add uses that same connection.

**The Temporal Grid**

Diagram of Cronofy's three capability pillars, managed scheduling and rescheduling, modular calendar and availability control, and meeting conferencing and transcription, all built on the Temporal Grid.

```mermaid
flowchart TB
  subgraph Cronofy
    direction TB
    The_Temporal_Grid[The Temporal Grid]
    subgraph Capabilities
      direction TB
      subgraph Managed_scheduling_and_rescheduling [Managed scheduling and rescheduling]
        direction LR
        Scheduling
        Scheduling_Controls[Scheduling Controls]
      end
      subgraph Modular_calendar_and_availability_control [Modular calendar and availability control]
        direction LR
        Availability
        Calendar_Events[Calendar Events]
        UI_Elements[UI Elements]
      end
      subgraph Meeting_conferencing_and_transcription [Meeting conferencing and transcription]
        direction LR
        Conferencing
        Meeting_Transcripts[Meeting Transcripts]
      end
    end
  end
  The_Temporal_Grid --- Capabilities
```

- Managed scheduling and rescheduling groups Scheduling and Scheduling Controls.
- Modular calendar and availability control groups Availability, Calendar Events, and UI Elements.
- Meeting conferencing and transcription groups Conferencing and Meeting Transcripts.
- All three pillars are built on the Temporal Grid, which covers applications, Organizational Units, data centers, webhooks, and the MCP Server.


The capabilities on top are grouped into three pillars:

- [Managed scheduling and rescheduling](https://docs.cronofy.com/developers/managed-scheduling/index.md)

- [Meeting conferencing and transcription](https://docs.cronofy.com/developers/conferencing-and-transcription/index.md)

- [Modular calendar and availability control](https://docs.cronofy.com/developers/calendar-and-availability/index.md)

Use them independently or together.

Each pillar has its own Authorization page saying which ways of obtaining
access suit it. [Connectivity](https://docs.cronofy.com/developers/temporal-grid/connectivity/index.md)
explains the ways of obtaining access, and how to choose between them.
How Cronofy connects to your users' calendar and conferencing services is
covered in [Connect with Cronofy](https://docs.cronofy.com/connect/index.md).


---
[Read in HTML](https://docs.cronofy.com/developers/temporal-grid/)

## In this section

- [Integration approaches](https://docs.cronofy.com/developers/temporal-grid/integration-approaches/index.md) — Choosing how to connect to Cronofy, depending on whether you're building for your own company's workflows or for your customers through your product.
- [Connectivity](https://docs.cronofy.com/developers/temporal-grid/connectivity/index.md) — How your application gets access to calendars and scheduling: at the organization, service account, or user level.
- [MCP Server](https://docs.cronofy.com/developers/temporal-grid/mcp-server/index.md) — MCP Server for interacting with the Cronofy service from an MCP Client. Typically with an agentic workflow tool.
- [Real-time scheduling](https://docs.cronofy.com/developers/temporal-grid/real-time-scheduling/index.md) — How Cronofy books meetings against live calendars and the availability people have approved in advance, and keeps them right as plans change.
- [Webhooks & workflows](https://docs.cronofy.com/developers/temporal-grid/webhooks/index.md) — The webhooks Cronofy sends through a meeting's lifecycle, so your application stays up to date and can drive its own workflows.
- [Data centers](https://docs.cronofy.com/developers/temporal-grid/data-centers/index.md) — Cronofy currently provides six data centers. One in the USA, the default, and others in Australia, Canada, Germany, Singapore and the United Kingdom. They are run as completely separate instances with no data flow between. This allows you to ensure data is kept within jurisdictional boundaries, eg. the EEA.