Core Concepts
Projects
Understand project isolation, security boundaries, environments, and domain configurations.
Overview
In Asiyst, a Project represents an autonomous workspace dedicated to a specific website, web application, or product experience. All resources—including avatars, knowledge sources, conversation transcripts, and API credentials—belong strictly to a single project.
Isolation Boundary
Project boundaries enforce strict security and compliance separation:
- Zero Cross-Talk: Knowledge indexed in Project A is never accessible or searchable by Project B.
- Dedicated Public Keys: Each project issues unique public SDK keys (
pk_live_...) tied exclusively to its authorized domain list.
- Independent Usage Tracking: Token consumption, session counts, and event metrics are isolated per project for clean billing and analytics.
Project Lifecycle
A project transitions through three defined statuses:
active: The project is operational and accepting live SDK sessions and API requests.
paused: Client connections are temporarily rejected with HTTP 503; configurations and knowledge remain intact.
deleted: The project is soft-deleted and scheduled for cryptographic purge after the data retention window.
Environments & Keys
Projects maintain two operating environments:
- Development: Ideal for staging servers and localhost testing with verbose debug logs.
- Production: Optimized for high concurrency, strict CORS validation, and latency-optimized inference.
Learn more in Project Overview and Project Settings.