Dubhe in the Obelisk Stack
How Dubhe Engine fits into Obelisk Labs workflows for contract development, indexing and API delivery.
Page-aware AI
Ask AI about this page
Get answers grounded in the live Obelisk docs set, with source links, selected-text explainers, and prompts for the next document to read.
Dubhe Engine is the Move-native foundation used across Obelisk Labs products. In this platform, Dubhe is not only a contract toolchain; it is connected to organization workflows for deployment, indexing and data access.
Where Dubhe Appears in This Product
You will see Dubhe workflows in three major areas:
- Contract Lab: create and iterate Move projects and revisions.
- Indexer Lab: provision Dubhe indexer services with per-tenant isolation.
- Channel/API surfaces: expose GraphQL and gRPC endpoints for application clients.
Operational Model
Obelisk uses an asynchronous provisioning model for reliability:
- User actions create provisioning tasks.
- Workers consume tasks and call provider adapters.
- Task status is written back for auditability and retries.
This gives consistent behavior across create, suspend, resume, redeploy and deprovision operations.
Recommended Reading
Notes for Production
- Confirm provider configuration before enabling production provisioning.
- Keep webhook secrets and worker secrets isolated per environment.
- Validate tenant isolation strategy for shared Postgres deployments.