An event belongs to one product
The edit happens where the entity was created: leave in HR, a hearing in legal. The Calendar keeps no second copy of the fact and cannot drift from it.
About
The Calendar is packaged as a standalone product, but it works as a platform foundation: the same role the file layer plays for the suite.
Why the suite needs a separate scheduling layer
Without one, every product grows its own date field, its own recurrence logic, its own reminders and its own take on time zones. Recurrence parsing written five times means five different sets of bugs on the day the clocks change.
The Calendar takes that work off the products and leaves them what they really own: the meaning of the event. In exchange it takes on everything to do with time and does it the same way for everyone.
What the product reliability rests on
The schedule updates right away
The product reports a change the moment it happens. An open tab refreshes instantly, nobody triggers a sync by hand.
Time does not drift between zones
An event keeps the moment and the zone it originated in. A daylight saving shift in one country does not move a meeting in another employee calendar.
Edits are never lost silently
If an event is changed from two devices at once, no edit disappears unnoticed. The person is shown both versions and asked to pick the right one.
The full set from day one
Two-way synchronisation with external calendars, shared and resource calendars, slot finding are parts of the product, not a separate add-on.
The perimeter is limited on purpose
The Calendar does not connect to external video services and does not parse personal mail looking for bookings. Video meetings are covered by A3.Meet, and the Calendar has no access to mail outside A3.Mail.
Reliability and data
- Servers
- In the Republic of Kazakhstan, as with the rest of the ecosystem.
- Data separation
- Each company schedule is isolated at the model level, not only by a filter in a query.
- Delivery
- Reminders and invitations go through a queue: a mail failure neither loses them silently nor sends them twice.
- Activity log
- Integration calls are logged, and the write rate is limited: a failure in one product does not touch the others.
- Deactivation
- When a subscription expires data is hidden rather than deleted. Disabling a product hides its events but keeps them.
- Freshness
- Availability and the schedule are recomputed continuously: the list of free windows never goes stale for hours.
Who builds the product
A3.Calendar is built by A3.Solutions alongside the rest of the suite: the A3.ID single sign-on, document management, HR, legal and finance products.