Domaniqo is iCal-first. Paste the calendar link each of your listings already publishes, and every stay it carries flows into one operational timeline — read on a schedule, normalized into one record shape, and traceable back to the feed it came from.
Domaniqo does not list your property, price it, or sell it. It does not push availability back to a platform. It reads the calendars you already publish and turns the stays inside them into work your team can actually run.
Calendar sources
If it publishes an iCal calendar, Domaniqo can read it.
Airbnb calendarBooking.com calendarVrbo calendarAgoda calendarYour direct booking calendarAny other iCal calendar
These are the standard iCal calendar exports each platform publishes for a listing — not direct booking-API integrations, which Domaniqo does not offer today. Platform names and trademarks belong to their respective owners.
How a feed is read
Four stages. Nothing invented in between.
01
Connect the calendar
Paste the iCal link from your listing. It is stored against that property with the source it came from. One property can carry several calendars at once.
02
Read on a schedule
Domaniqo refreshes active calendar feeds on a short recurring cycle to keep booking information current.
03
Normalize into one record
Reserved becomes an observed stay, Not available becomes a block. Each import writes a canonical booking record plus an audit entry, so you can trace any stay back to the read that created it.
04
Reconcile what changed
Re-reading is idempotent, so nothing is created twice. A cancelled or vanished stay is reconciled on a deliberate delay rather than dropped, and a stay your team has already checked in or out is never overwritten by a calendar.
Why this is more than a calendar import
Calendar-feed visibility with engineering depth.
Traceable Import History
Every import writes an audit entry beside the booking record it produced. You can ask of any stay: which feed carried it, and when did we read it.
Conflict Detection
When two calendars on the same property disagree about the same dates, Domaniqo surfaces it instead of letting the later read quietly win.
Feed Health at a Glance
Every connection carries its own status and the time of its last read. A feed that has gone quiet is visible before a missing arrival is.
Nothing Vanishes Quietly
A stay that disappears from a feed is not deleted on the spot. It goes onto an absence clock and is reconciled with a recorded reason, so a one-off bad read cannot erase a real booking.
Several Calendars, One Property
A villa listed in three places has three calendars. Domaniqo reads them as one set for that property, so the timeline is the whole property, not one platform’s view of it.
The Calendar Never Overrules Your Team
Once a worker has checked a guest in or out, no later calendar read can undo it. The feed owns the reservation. Your team owns what happened on the ground.
Ready to connect your calendars?
Start with the properties you run today. Add the rest whenever you are ready.