Custom software for tourism and hospitality.

Tourism processes personal data on contractual basis (bookings) and sometimes sensitive data (dietary preferences, declared medical conditions). Under Law 21.719 (effective December 2026) they must publish a processing policy carrying the twelve contents of art. 14 ter, declare the lawful basis per flow, run an ARCO+ request channel with identity verification answered within thirty calendar days (art. 11) and evidence the security measures adopted (art. 14 quinquies). If the hotel sends data outside Chile, the international transfer needs a lawful ground and the policy has to disclose it (art. 27 and art. 14 ter, letter h). With European or Brazilian guests, GDPR and LGPD need mapping too.

Not by default. When the project requires it, custom API integration is built. What we do offer by default is a custom multi-language site with a simple booking engine, and the post-booking relationship layer (notifications, AI assistant). If the client already has a channel manager, we integrate it as a specific module.

A multi-language site without a booking engine is one module; with a custom booking engine and payment gateway integration (Flow.cl, Transbank, Stripe) it becomes several modules over a dedicated database. Indicative: from 80 UF plus VAT for a base scope of one module and a documented stack; from 150 UF plus VAT for a base scope of several modules over a dedicated database. The final figure is set during discovery and depends on how many systems are involved, the state of the code, the third-party integrations, how many modules are involved and the state of the code being integrated. This is not an offer. After reviewing your written brief at /en/contacto, we deliver a formal quote in 24 to 72 hours.

Yes. Docker Compose stack runs on aGo-managed VPS (Hetzner, Hostinger, AWS, Azure or Google Cloud). For operators with highly seasonal traffic we evaluate auto-scaling infrastructure on hyperscalers. The project defines the choice, not the other way around.

Yes. Stripe for international payments (card + local currency), Flow.cl or Transbank for Chilean payments. Multi-currency conversion and visualization is built into the storefront. Each gateway has its own client KYC requirements; we accompany you during integration.