Naming note. This product was internally called
AguaAzul during 2026-05-15 → 2026-05-22 (after the first
dogfooded property, Agua Azul). The locked consumer brand is
CasaOps. Agua Azul now refers only to the
specific Phase 1 dogfooded property; STR-ops still appears
as the legacy internal name for the Phase 1 backend service in some
URLs and code paths pending a follow-up rename.
What it is planned
CasaOps is an AI-native short-term-rental management platform targeting the Mexican market. Two-phase plan:
- Phase 1 — operate one property (the Agua Azul property) end-to-end on the in-house tooling. Prove the model on real bookings before generalizing.
- Phase 2 — productize into SaaS for MX hosts running 1-5 units. Pricing in MXN, locally-relevant feature set.
Kicked off 2026-05-15. Current state: research + 8 wireframes complete; no code yet on the customer-facing SaaS, Phase 1 backend live (see below).
The wedge — why this is different
The Mexican STR market is underserved by US-centric platforms in three specific ways CasaOps leans into:
| Wedge | Why MX hosts care |
|---|---|
| CFDI auto-issue | Every business transaction in Mexico requires an electronic invoice (CFDI 4.0) filed with SAT. Tools that don't auto-issue these put the compliance burden on the host. CasaOps issues automatically per booking. |
| WhatsApp-first | Guest comms in MX run through WhatsApp, not in-platform inboxes. CasaOps's guest-comms layer is WhatsApp-native, with the property-management dashboard a secondary surface. |
| MXN pricing | Hosts price in pesos, not USD-translations-at-checkout. Reporting and payout flows reflect this. |
STR-ops — Phase 1 production deploy
The Phase 1 backend, still branded internally as STR-ops for the moment, is running at casaops.sandpointstudios.ltd (formerly strops.sandpointstudios.ltd) — managing the Agua Azul property's bookings, guest comms, and operations.
| Code | /opt/strops/ on vigil-server (directory rename to /opt/casaops/ deferred) |
| Backend port | 8015 (remapped from default 8000 due to collisions) |
| Frontend port | 8081 (remapped from default 80 due to collisions) |
| Public surface | casaops.sandpointstudios.ltd via the multi-tenant cloudflared tunnel |
| Gate | CF Access (SPS allowlist; not customer-facing yet) |
Domain ownership quirk
casaops.mx and casaops.app live in the secondary Cloudflare account. Like haulhard.com, these "orphan" domains landed in the secondary CF account (teaganwins@gmail.com) by accident when purchased rather than the primary (twistedyeti@gmail.com). Move-Domain can transfer them in ~30s when needed.
The consumer-facing customer-acquisition domain is casaops.mx once it moves accounts; casaops.sandpointstudios.ltd is the same-account alias serving the dev team and Phase 1 today.
Topology (Phase 1 → Phase 2 sketch)
flowchart TB
subgraph P1[Phase 1 — single property]
PROP[Agua Azul property]
STROPS[CasaOps backend
vigil-server :8015] STROPS_FE[CasaOps frontend
vigil-server :8081] SAT[SAT / CFDI
auto-issue] WA[WhatsApp Business
guest comms] PROP --> STROPS STROPS --> SAT STROPS --> WA STROPS_FE --> STROPS end subgraph P2[Phase 2 — SaaS for MX hosts 1-5 units] CASA[casaops.mx
multi-tenant SaaS] HOSTS[1-5 unit hosts] HOSTS --> CASA CASA --> SAT CASA --> WA end P1 -.lessons + multi-tenancy refactor.-> P2
vigil-server :8015] STROPS_FE[CasaOps frontend
vigil-server :8081] SAT[SAT / CFDI
auto-issue] WA[WhatsApp Business
guest comms] PROP --> STROPS STROPS --> SAT STROPS --> WA STROPS_FE --> STROPS end subgraph P2[Phase 2 — SaaS for MX hosts 1-5 units] CASA[casaops.mx
multi-tenant SaaS] HOSTS[1-5 unit hosts] HOSTS --> CASA CASA --> SAT CASA --> WA end P1 -.lessons + multi-tenancy refactor.-> P2
Dependencies
- vigil-server — Phase 1 backend + frontend hosting.
- Cloudflare Access + tunnel — public surface for casaops.sandpointstudios.ltd.
- SAT (Mexican tax authority) — CFDI 4.0 e-invoice filing via SAT API or a Mexican PAC (Authorized Certification Provider).
- WhatsApp Business API — guest-comms surface.
- Bookings source — TBD (Airbnb / Vrbo / direct), reading reservations into the Phase 1 backend.
Roadmap
- Now: 8 wireframes done; convert to clickable prototypes; validate the WhatsApp-first guest-comms flow against real Agua Azul guests.
- Phase 1 (in progress): backend running the Agua Azul property end-to-end. Iterate based on real bookings.
- Phase 2 prep: multi-tenancy refactor — same shape as TimeKeep's XDEC-128 (orgs + memberships). One host per tenant; staff/co-hosts as members.
- CFDI integration: pick a PAC, integrate, test on Agua Azul's own bookings before generalizing.
- Phase 2 SaaS launch: casaops.mx as the customer-acquisition domain.
- Domain housekeeping: Move-Domain casaops.{mx,app} from secondary to primary CF account when Phase 2 is closer.
- Internal rename: retire the
STR-ops/strops.//opt/strops/legacy names in code + filesystem in a follow-up PR.
Related
- TimeKeep — the multi-tenant shape that Phase 2 will mirror.
- FinishOps + OneCut — sibling B2B-tooling JV products in the portfolio.
- Shared infrastructure — Cloudflare account topology, the multi-tenant tunnel that fronts casaops.sandpointstudios.ltd.