One place, one stay

Live the city from within.

A calm apartment for four, made for walking, slow cooking and returning without a rush.

Try an enquiry→

City apartment

Everything you need. Nothing in the way.

Natural light, honest materials and a guide that starts at your doorstep.

4 guests
2 bedrooms
1 property

A stay with context

A guide that fits in your pocket.

Markets, coffee, architecture and walks selected from the website.

Basic · Logic2B Estancias

How a direct enquiry could arrive.

Compare three fictitious enquiries and the context an email could contain. The demo asks for no personal data, sends no message, queries no inventory and creates no booking.

Local simulation · no deliveryNivora One

Choose one of three fictitious cases to see the context the property could receive.

Email previewFictitious enquiry · 3-night city break

To: bookings@nivora.example
From: Marta · fictitious person
Stay: 16–19 April 2027
Guests: 2 guests
Property: Nivora One · fictitious fixture

We would like to walk the city from the apartment and know whether the guide includes markets and quiet routes.

This preview only changes in your browser memory. It collects no personal data, sends no email, queries or holds no inventory and creates no booking. Reloading restores the first example.

Readiness contract

File required before delivery

Choosing a fictitious case only changes the preview: it validates zero delivery conditions. All thirteen require separate data policy, configuration, tests and acceptance.

Validated conditions 0 / 13

01
Owner
Direction accepts scope and an accountable owner is responsible for content, delivery and incidents.
Not validated
02
Lawful basis and purpose
Purpose, applicable lawful basis or consent, minimum data and retention are agreed before collecting information.
Not validated
03
Permissions
Templates, configuration, delivery and audit use separate, revocable least-privilege access.
Not validated
04
Provider category
The transactional email category must be validated per project; no brand, account or provider is selected.
Not validated
05
Configuration reference
Opaque reference to be defined outside the browser; the demo contains zero keys, domains, accounts, live addresses or secrets.
Not validated
06
Templates
Subject, body, languages, sender identity, boundaries and legal copy need versioning and human review.
Not validated
07
Routing
Origin, destination, reply and escalation are verified with test routes; only reserved `.example` addresses appear here.
Not validated
08
Idempotency
A stable reference must represent one logical delivery and allow retries without duplicates.
Not validated
09
Failures and retries
Timeout, rejection, quota, degradation and uncertain outcome require limits, bounded retries and manual recovery.
Not validated
10
Audit
Reference, template version, actor, outcome and correlation are recorded without PII, message, address, key or secret.
Not validated
11
Acceptance
Direction accepts content, languages, test routes, failures and receipt evidence before authorising delivery.
Not validated
12
Kill switch
An independent control blocks new product deliveries without affecting the separate commercial lead intake.
Not validated
13
Rollback
The last accepted template and configuration must be restorable and uncertain outcomes reconciled.
Not validated