Security and access
Control who can build, who can use an application and who can publish a release.
Organisation and project access
A Software House installation belongs to one organisation. Give people access through membership, teams and project roles. Building, publishing and changing access have separate permissions.
Software House supports multi-factor authentication. You can also connect an identity provider through OpenID Connect.
Project isolation
Each project runs in a separate container for its files, tools and agent work. Permissions determine which secrets and capabilities it receives. Network policy restricts outbound access.
Previews and releases
Previews require project access. Publication releases a specific version into a separate runtime; later development does not change it. Organisation policy can require approval from another person.
Published applications can be public, open to organisation members or restricted to selected people and teams.
AI providers
Coding agents and insights assessments use external AI providers. Prompts, code, files and task output may be sent to the selected provider. Choose accounts and agreements that match your organisation's data requirements.
Activity records
Builds, releases and access changes record who took the action. Workflow approvals are linked to a particular run.
Backups and recovery
Backup retention, recovery and support access depend on your service configuration. Contact us to discuss those requirements.
Application review
Review and test generated software before publishing it, including its handling of data and access.
To report a security issue, email contact@blazingbanana.com.