Meeting times without the back and forth
A3.Calendar finds a common slot from the busy time of people and rooms, gives guests a booking link and keeps personal, team and A3 product events in one grid. Everyone sees them in their own time zone.
A platform layer, not another calendar app
What A3.Calendar gives each person
One schedule covers the tasks of different people inside the company and outside it. Everyone gets their part without getting in the way of others.
Employees
Their own schedule in six views, an event from one phrase, reminders on the phone, and Outlook or Apple Calendar over CalDAV for those who prefer them.
Quick creation and drag and dropManagers and assistants
Team availability on one timeline, a common meeting time without back and forth, and a manager’s calendar kept by an assistant with a mark of who created each event.
Team availabilityAdministrators
Departments, employees and working hours, meeting rooms and equipment, the holiday calendar of five countries and calendar rights.
Departments and employeesClients and partners
A booking link instead of agreeing in a chat: the guest picks a free slot, receives emails in their language and cancels from the email.
Booking links
The whole schedule, not a grid of days
Products stop writing their own recurrence, time zone and reminder logic. It lives here, in one place, and behaves the same for everyone.
Personal and team calendars in one grid
Personal, team and resource calendars stack on top of each other through checkboxes. A source filter shows, for example, only the hearings coming from legal.
Stored in UTC, rendered on the client
An event keeps the moment in UTC plus the zone it originated in. Daylight saving is handled when the rule is expanded, not patched in by hand.
Recurrence by the RFC 5545 standard
The rule is stored as a string and occurrences are computed per request. Editing one occurrence, cutting the series and editing the whole series are separate actions, as in any mail client.
Meeting slot finder
A common window is found across the availability of participants and rooms. When there is no full overlap, you get the slots with the most people free, not an empty answer.
Booking links for outside guests
The guest picks a free window themselves, emails travel in their language, and the link quota is returned whichever side cancels.
Outlook and Apple Calendar over CalDAV
Two-way synchronisation by RFC 4791, plus a revocable read-only subscription link for external clients.
Public holidays across five countries
Holidays and shifted working days come from the shared ecosystem library. An account declares its own days on top, and each event decides what to do with a non-working day.
Works like the calendar you know
The architecture stays under the hood. Day to day it is a familiar, convenient calendar with nothing new to learn.
Six views
Month, week, 4 days, day, year and agenda.
Event from a phrase
“Team sync tomorrow at 10:30 with Ivan” becomes an event at once.
Drag and drop
Move and resize with a mouse or a finger, undo the last action.
Search
By title, description, location, attendees and category, with saved queries.
Keyboard shortcuts
Navigate and create without a mouse in Russian and English layouts.
Dark theme and app
A light and a dark theme, installation on a phone and a computer.
How a product fact becomes a line in the schedule
The product calls upsert
HR approved a leave, legal received a hearing date. The product reports the change itself: the Calendar never polls products.
The Calendar stores a projection
Event identity is the triple of product, entity type and entity id. A repeated call updates the record instead of creating a second one.
Each person sees their own time
The moment is stored in UTC together with its origin zone. A colleague in Almaty and a colleague in Ulaanbaatar see one event in their own hours.
Edits go back to the source
A product event is not editable inside the Calendar: the link leads back to the leave or hearing card, so the projection never drifts from the source of truth.
The product owns the fact. The Calendar owns its schedule
This boundary explains the rest of the product: why product events are not edited in the grid, why an event has exactly one owner and why sign-in and the subscription go through A3.ID.
How this works across the suite- An event has exactly one owning product, so there is nothing for a third party to detach
- Repeating upsert and remove on the same triple is safe and creates no duplicates
- Every update carries the version the caller last saw
- A version mismatch returns 409 and both versions to choose from instead of overwriting silently
- Deactivating a product hides its events without deleting them
- Sign-in, the companies of the domain and the subscription come from A3.ID: the Calendar has no separate sign-up
Five countries in different zones is a requirement, not a detail
A shared meeting lands in each participant calendar in their local time. A national holiday closes the day for everyone, while a personal working schedule still applies.
- Kazakhstan
- Russia
- Kyrgyzstan
- Uzbekistan
- Mongolia
Servers are located in the Republic of Kazakhstan, as with the rest of the ecosystem.
Who writes events into the Calendar
The product stays the owner of the business fact: what kind of leave this is and what hearing that is. The Calendar owns only its schedule. A product that needs a grid inside its own interface embeds the widget.
Connect the schedule of the whole suite
Personal, team and resource calendars, reminders, the slot finder, booking links and external synchronisation are available from day one.