Docs

Most teams do not need to make a big infrastructure decision on day one. Start by deciding what you want to prove: a quick hands-on trial, a managed Qlik Cloud connection, or a gateway your own team will operate.

That choice shapes the security conversation, the Qlik admin involvement, and how quickly your users can start testing.

• Use a customer or partner-managed machine for short trials with sample, public, or approved non-sensitive data.
• Choose hosted gateway access when you want Raptor to provide a managed route for an approved Qlik Cloud tenant.
• Choose a customer-hosted Enterprise Gateway when your security team wants your organization to run and manage the gateway.
• Add migration or specialist services when you have a defined project such as QlikView migration, Power BI migration, modernization, or managed analytics delivery.

You do not need a full technical design before registering. A few practical details are enough to help your team, partner, or Raptor support guide the account setup.

• Which Qlik platform you use: Qlik Cloud, Qlik Sense Client-Managed, or both.
• Who owns the Qlik environment and can approve access for testing or production use.
• Who should use Raptor MCP first: internal developers, analysts, administrators, consultants, or partner delivery users.
• Whether you want a self-managed trial, partner-supported trial, hosted gateway access, customer-hosted gateway access, or a project-led migration/service engagement.
• How you prefer to buy: card checkout, invoice request, partner referral, or partner-managed delivery.

A trial is for focused evaluation, not for bypassing your normal security controls. Keep production systems, confidential customer data, and long-lived credentials out until the trial machine and Qlik access are approved.

When you are ready for real Qlik access, use the hosted gateway or Enterprise Gateway setup path that matches your security review.

• Use sample, public, or approved non-sensitive content during the trial.
• Use an authorized Qlik Cloud administrator when setting up hosted gateway access.
• Treat gateway tokens like passwords: store them securely, do not share them, and revoke them if they are exposed.
• For long-running work, use a supported client and expect normal reconnect behavior if a session expires.