- Scenarios where alternatives are better
- When a self-serve, low-touch product with published pricing and a free trial is required.
- When the organization lacks technical resources to integrate and maintain an API-driven cruise distribution layer.
- When a procurement process requires abundant third-party reviews as a prerequisite; IST’s public review footprint appears limited.
- When procurement requires pre-validated compliance documentation (SOC 2 / ISO 27001) to be publicly available prior to engagement.
- When the buyer’s primary need is complex dynamic packaging and a vendor explicitly optimized for packaging workflows is preferred.
- Red flags in the buying process to monitor
- Vendor statements about connectivity without a current, verifiable list of supported cruise lines in target markets.
- Unclear delineation between real-time API connectivity and offline feed capabilities.
- Lack of clear SLAs, incident communication commitments, or escalation processes in contract drafts.
- Current limitations acknowledged by the vendor
- No explicit public "known issues" page was found in the sources reviewed.
- Features on the roadmap
- Roadmap details are not publicly documented in accessible sources.
- Scale limitations
- Not publicly documented.
- Security or compliance gaps
- Public disclosure gap: certifications (SOC 2 / ISO) and enterprise security features are not clearly documented on marketing pages.
- API limitations or integration constraints
- Specific API-level documentation items (rate limits, sandbox availability, webhook support, versioning policies) were not available in public-facing sources.