Your cloud or Ahamo Cloud
Choose the placement of enterprise build sandboxes and published apps independently.
On this page
Availability: Customer-cloud sandboxes and customer-cloud publishing are enterprise capabilities configurable in your tenant. Available destinations depend on your enabled offering and the connected customer environment.
There are two separate placement decisions: where AI builds are executed, and where the finished app runs. You can keep the Ahamo building experience while using approved customer-cloud environments.
Where building happens
A build sandbox is the isolated environment used to work on an app and validate changes. Enterprise tenants can configure sandboxes hosted in customer cloud instead of Ahamo-hosted build infrastructure.
Your team should establish the approved environment, required connectivity, access responsibilities, and the data allowed during building. A preview is part of the build and review process; it is not a substitute for a production deployment.
Where the finished app runs
Enterprise apps can be published to customer cloud rather than Ahamo Cloud. Choose a connected, approved destination in the tenant's publishing configuration.
The production destination needs the services the app actually uses, including its database, authentication, storage, and secrets. A custom domain changes the address people use; it does not by itself move the app or its data to customer cloud.
Keep the decisions separate
| Choice | Question it answers |
|---|---|
| Build sandbox | Where does the builder execute and validate changes? |
| Model configuration | Which AI models process the work? |
| Publishing destination | Where does the released app serve its users? |
| App data and services | Where are records and supporting services operated? |
Selecting customer-cloud sandboxes does not automatically relocate model processing or an already-published app. Review the complete configuration for your tenant and project.
Agree on operating responsibilities
Before a production release, assign owners for cloud access, costs, monitoring, backups, secrets, and incident response. Confirm the supported deployment environment with your Ahamo enterprise setup; customer-cloud support does not mean every provider or runtime is interchangeable.
Use safe test data to verify an end-to-end build and release to the selected destination. Check the actual production URL and its access rules from outside the builder.
Next: Publish an app or review app ownership.