Version 1.1.0

What's changed

• Server startup and service paths. Fixes cloud-init formatting and service paths so the generated startup configuration and installed services use the intended files and directories.
• Safer configuration and administrator access. Adds previews for configuration changes, preserves existing settings and secrets, and provides dedicated commands to update administrator access or restrict an app without hand-editing generated policies.
• Capacity estimates and a smaller starting point. Uses shared app metadata for capacity estimates and required services. The setup guide starts with one app, and new installations default to a 100 GB boot volume. Estimates are for planning; actual usage and Oracle billing still need monitoring.
• Native Windows setup checks. Adds a PowerShell entry point for the setup doctor, structured results, and explicit confirmations for budget, account ownership, backups and recovery. Skipped or unknown checks remain unfinished.
• Release and dependency integrity. Strengthens checks of release contents and file hashes, aligns the Terraform provider lock with Terraform's registry, and validates generated startup configuration and allocation guardrails.
• Encrypted state recovery and reviewed shutdown. Adds encrypted Terraform recovery bundles and an agent-guided OCI CLI workflow for an independent, private, versioned state bucket. Recovery copies are kept outside the workstation and Oracle. The shutdown guide reviews resources and retained data before deletion, then removes the state bucket last.

Using this release

Download the kit through your existing Brain Stack customer access, extract it, and open START-HERE.html. The updated workflow still requires your Oracle account, credentials, app settings, DNS and first-login configuration. Optional model providers, email services and backups may need separate accounts and incur charges.

For an existing installation, follow the included upgrade and recovery guides. Back up first and preserve your configured settings, keys, state and app data; do not overwrite a live installation with a fresh kit.

Automated configuration and package checks do not replace a complete acceptance run on a live OCI ARM server. Verify startup, access and recovery for your selected apps before relying on the deployment.