> ## Documentation Index
> Fetch the complete documentation index at: https://docs.satyakod.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pilot workspaces

> What a 30-day pilot includes, its limits and what happens when it ends.

A pilot lets your team try Satyakod on real packs before signing a contract: issue codes, print
them, scan them and see verdicts, alerts and reports, exactly as a live workspace does.

| | Pilot | Live workspace |
| - | - | - |
| Length | 30 days from the start date | Your contract term |
| Codes | Up to 1,000 across GS1 Signed and Private Code | Your plan's quota |
| Team | Up to 10 people | Your plan's seats |
| API keys | Test keys only (`vrq_test_…`) | Test and live keys |
| Features | Scale's: Code Studio with one design, Zebra printers and SAP, the WhatsApp verify bot | Those in your [plan](https://docs.satyakod.com/guides/plans.md) |
| Everything else | Products, batches, scan page, alerts, reports, integrations | Same |

SSO, SCIM provisioning and audit log export are part of the Enterprise plan and are not included
in a pilot.

Every page shows a **Pilot** banner with the days left and codes used, and a link to talk to us
about going live.

![The pilot banner with days left and codes used](https://docs.satyakod.com/images/screenshot-placeholder.svg)

The pilot banner with days left and codes used

## When the pilot ends

From the end date, the workspace stops issuing new codes. Codes already printed keep verifying,
and your data stays: going live turns the same workspace into a customer workspace, so batches,
scans and settings carry over. Create live API keys once you have gone live.

ERP batch sync (SAP S/4HANA) skips orders that would pass the pilot's code limit and counts them
as skipped in the sync log.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.