Accounts and permissions
Use your website account to choose an instance and manage your organisation’s access. It requires email verification and supports an authenticator. Manage your website sign-in security.
Accounts inside a Software House installation are separate. Use organisation membership, teams and project roles to grant access there. Building an app, publishing it and changing access are separate permissions. Installations support authenticator codes and OpenID Connect sign-in.
Project execution
Project agents and tools run in separate containers. The project’s permissions determine which files and capabilities are available. The installation enforces network controls and storage limits.
Administrators choose which provider connections a project can use. Check the generated app and how it handles data before publishing it.
Private previews and releases
Private previews require project access. Published apps run separately from the project under development, so colleagues can keep using a release while changes are being made.
You can make an app public or restrict it to organisation members, selected people or teams. Publication can require approval by someone other than its author.
Data sent to AI providers
Codex, Claude Code and automatic assessments send requests through the provider connections you configure. Those requests can include prompts, source code, files and task output. Check that your provider agreement covers the data you plan to send.
Your server hosts Software House. AI requests still need an internet connection to the configured provider.
Activity and recovery
The activity record shows who built or published a tool and who changed access. Workflow decisions are recorded against the run they concern.
Encrypted backups include platform and application data. You can test a restore in isolated resources before replacing live data, which requires a maintenance pause. Keep independent recovery keys and a separate recovery plan for a lost server or cluster, such as provider snapshots.
Report a security issue
Email contact@blazingbanana.com with the affected version and a brief description. We will agree a way for you to send sensitive details.