> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/sdks/web-integrations/hosted-solution-quick-guide.md).

# Hosted Solution

Build hosted KYC, AML, and identity verification flows with ComplyCube's branded verification pages.

## Overview

**ComplyCube Flow** is our secure, fully hosted KYC and identity verification solution. It provides a customizable, branded page that allows you to verify customers quickly with minimal code.

When you initiate a Flow session, a unique ComplyCube URL is generated. Redirect your customers to this URL to collect consent and guide them through the verification process. Once the session is completed, the customer is redirected back to your specified return URL.

![ComplyCube Hosted Solution](https://648014528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flv7UhJvTbxeq4s3KwQpn%2Fuploads%2F4A576Mf2gafASX0uDHfQ%2Fhosted_solution-drop-shadow.png?alt=media\&token=f9eee610-7fe9-486f-9de0-3d188e7ce948)

## Benefits

Flow makes it simple to deliver a first-class KYC experience:

* **Fast to integrate**: Go live quickly with minimal engineering effort.
* **UX-optimized**: Guided, conversion-focused flows with built-in error handling.
* **Mobile ready**: Fully responsive design that works seamlessly across devices.
* **International**: Multi-language support for global coverage. View [supported languages and locale codes](/documentation/sdks/supported-languages.md).
* **Customizable**: Configure verifications, stages, colors, and branding (logo and text).
* **Data-compliant**: Simplified compliance, as sensitive PII never resides on your infrastructure.

## Interactive demo

{% @arcade/embed url="<https://app.arcade.software/share/DQYWw1OnvTXJpuguEsVp>" flowId="DQYWw1OnvTXJpuguEsVp" fullWidth="false" %}

## Integration modes

The Hosted Solution can be integrated in two different ways, depending on your needs:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Workflow Integration</strong></mark></td><td>Use the Workflow Designer to build your customer KYC journey and simply load it. This is the preferred option for most use cases.</td><td><strong>Recommended</strong></td><td><a href="/documentation/sdks/web-integrations/hosted-solution-quick-guide/hosted-solution-quick-guide.md">Workflow Integration</a></td></tr><tr><td><mark style="color:blue;"><strong>Check-Driven Integration</strong></mark></td><td>A lower-level approach where you directly control individual journey screens and checks. It's best suited for advanced use cases.</td><td></td><td><a href="/documentation/sdks/web-integrations/hosted-solution-quick-guide/hosted-solution-quick-guide-1.md">Check-Driven Integration</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.complycube.com/documentation/sdks/web-integrations/hosted-solution-quick-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.