> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/getting-started/compare-and-faq/poc-guide.md).

# PoC Guide

A PoC is a program provided for a limited period to validate the usability of the Hackle solution in a real service environment.

It operates under the following conditions in accordance with internal policy.

## PoC Policy

{% hint style="danger" %}
A PoC is provided once per company (legal entity).

If usage is deemed abnormal or excessive, the PoC may be terminated.
{% endhint %}

<table><thead><tr><th width="160.16796875">Category</th><th>Description</th></tr></thead><tbody><tr><td>PoC Duration</td><td>Including the SDK integration period, <strong>up to 3 weeks from the time the Workspace is provided</strong>.</td></tr><tr><td>Provided Traffic</td><td>Including test traffic, <strong>up to 10 million events are provided free of charge</strong>.</td></tr><tr><td>Billing Policy</td><td>Any usage exceeding the complimentary amount will be charged at KRW 0.3 per event in accordance with our standard policy.<br>However, these costs can be included in contract negotiations when converting to a full contract.</td></tr><tr><td>Features Provided / Scope</td><td>Certain features such as Raw Data upload &#x26; export may not be available.<br>The scope must be agreed upon in advance.</td></tr></tbody></table>

## PoC Scope

During the PoC period, the focus is on verifying the proper technical operation of SDK integration, event collection, and experiment implementation — not on hypothesis validation with actual data.

You can pre-verify whether the Hackle solution operates stably in your real service environment before converting to a full contract.

{% hint style="warning" %}
For native apps, there are technical constraints such as review and update periods (1\~2 weeks), so we recommend running experiments in the web (Web) area to achieve meaningful validation within the 3-week PoC schedule.

If you unavoidably need to proceed in the mobile app native area, we recommend selecting one platform — either Android or iOS — to reduce schedule risk.
{% endhint %}

## PoC Process (Support Structure)

{% hint style="info" %}
Communication and technical support during the PoC period are conducted through the Slack channel.

Workspace and Slack channel invitations are sent to the primary contact's email, and additional team members can be invited freely by the customer.
{% endhint %}

* Dedicated PoC Workspace and Slack channel setup
* Kickoff meeting facilitation
* Key support details
  * In principle, experiment and analysis design is performed by the customer, and Hackle provides guidance to support a smooth onboarding experience.
  * Hackle support includes: SDK integration review, configuration guidance, periodic usage monitoring, and issue response
* Post-PoC result review and follow-up discussion meeting facilitation

## PoC Wrap-up

{% hint style="success" %}
The PoC review meeting is held at the end of the PoC period.
{% endhint %}

* After the PoC ends, a meeting is held with the customer to review results and discuss whether to adopt the solution and next steps for collaboration.
  * Sharing of opinions on PoC validation points
  * Sharing of Hackle's review of the customer's usage during the PoC period
  * Support for estimating expected traffic and providing a usage quote to facilitate contract review
* The PoC review meeting is held within 5 business days from the PoC end date.
* Once the PoC period ends, Dashboard access will be restricted.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hackle.io/en/getting-started/compare-and-faq/poc-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.