Open source · Oracle Cloud Infrastructure
Cloud sandboxes take a ticket and a week to get, and nobody ever deletes them. This builds them from a chat inside your own OCI tenancy — and destroys them when their time is up.
No card needed. It installs on an Oracle Cloud Free Tier account on Always Free resources — or on a paid tenancy for the full set.
Watch it on YouTube: youtu.be/nuHfzOqG4io — chat, priced plan, running sandbox, destroyed.
You describe the environment you need in plain English. The assistant plans the OCI resources, prices them from Oracle's published price list, provisions them with Terraform through OCI Resource Manager, and hands back the URLs and credentials. Each sandbox carries a lifetime of 1 to 30 days and a budget, and a reaper destroys it when the time expires.
| Ask for | You get |
|---|---|
| A database to explore or wire into agents | Autonomous Database with Select AI and REST enabled, a chat UI, an MCP endpoint |
| Your app from a Git folder with a Dockerfile | The image built inside OCI, served over HTTPS |
| An AWS Lambda or any small handler | An OCI Function — Lambda code runs unchanged, optionally scheduled |
| A Glue or Spark job | An OCI Data Flow application, optionally writing Iceberg tables |
| An Airflow plus Spark pipeline | Airflow with your DAGs, Data Flow, Data Catalog, gold tables in Oracle |
| Queues, NoSQL, Kafka, buckets | OCI Queue, NoSQL tables, a Kafka cluster, Object Storage |
The reason nobody deletes a cloud sandbox is that deleting it is somebody's job and nobody's priority. Here it isn't a job. Every environment is created with an expiry and a budget. When the clock runs out the stack is destroyed, and every card has a Destroy button for sooner.
The install is a single OCI Resource Manager stack. The application, the container-instance workers, and the calls to OCI Generative AI all run inside your own account. Users sign in to the app with their own login and need no OCI account of their own.
Credentials never reach the model. When a stack needs a password, the assistant asks for it in a field on the page. The value goes to the resource, not to the AI. Image builds run inside OCI with kaniko, so no laptop ever holds cloud credentials.
Describe your AWS setup and it maps each piece, then builds it:
Every proposal comes with a cost table built from Oracle's live price list, broken down per component, with free allowances and per-use services called out. A paid Autonomous Database runs roughly $500 a month while it exists, so the assistant defaults to pay-per-use pieces and prices the database as an option you can drop.
The usual reason a tool like this never gets tried is that it wants a paid tenancy before you can see it work. It doesn't. Pick Edition: free on the install form and it runs on an Oracle Cloud Free Tier account with no payment method attached, using Always Free resources only.
| Free Tier edition | Standard edition | |
|---|---|---|
| Account | Free Tier, no card | Pay As You Go or paid |
| Workers | One Always Free Arm VM running the worker under podman | Container Instances, 1 to 10 |
| Assistant | Google Gemini, with your own free key | OCI Generative AI |
| Sandboxes build | Autonomous Database 23ai, NoSQL, Object Storage, and containerised apps on the Arm VM | Everything |
What Always Free does not include is declined up front rather than failing minutes into a build: Kafka, Functions, Data Flow, Data Catalog, Queue, API Gateway, and paid database tiers. Always Free allows two databases per tenancy and the control database is one of them, so it's one database sandbox at a time. Install in your home region.
One Resource Manager stack, about 15 minutes, run once by a tenancy administrator. A Free Tier account is enough for the Free Tier edition; the standard edition needs Pay As You Go or a paid account. Read the prerequisites first — they list exactly what the install creates and what it grants.
Install this into your tenancy. Developers ask for what they need in a chat instead of raising a ticket, and get a running environment with links and credentials in minutes rather than a week.
Give every environment an expiry when it is created. Here that is built in — 1 to 30 days plus a budget, enforced by a reaper that destroys the stack automatically.
Yes. The Terraform for the install and for every sandbox type is public on GitHub, so you can read exactly what gets created in your tenancy and what permissions it is granted before you run anything.