Settings & Configuration
Configure your Bynary deployment, from personal preferences to organisation-wide AI and GitHub connections, team management and deployment infrastructure.
Settings in Bynary are organised by scope: your account, your organisation, people and platform administration. Access to each section depends on your role. Project-specific options, such as PM mode, review gates and MCP servers, live in each project's settings.
The settings page with sidebar navigation and AI connectivity.
Open AI Connectivity
Add Anthropic Credentials
Open GitHub Connectivity
Settings are organised by access level:
Your personal details, and a toggle to show advanced features in the navigation.
Your organisation's name.
Anthropic API key and Claude subscription token, encrypted with AES-256-GCM.
GitHub App registration and installation, or a Personal Access Token.
Invite members, manage roles and organise teams. Teams can override organisation credentials.
Web search, preview deployments through Coolify, model pricing, editable AI prompts, supervisor monitoring and error logs.
A record of who did what, and when.
Documentation types, PM mode, scope and approach review gates, preview deployment toggle, environment variables and MCP servers.
Are my API keys stored securely?
Yes. API keys, tokens and MCP credentials are encrypted with AES-256-GCM before being stored, and decrypted only at the point of use.
What roles are available?
Bynary has 4 roles: Super Admin (platform administration), Admin, Member (full workflow access) and Viewer (read-only). Admin can be granted for the whole system, a team or a single project, and inherits downward.
Which AI model does Bynary use?
Model selection is automatic. Bynary routes each task to a suitable Claude model, and every call's cost is logged.
How do MCP servers work?
MCP (Model Context Protocol) servers give the AI access to external tools. Configure them per project using one of 10 presets, such as Supabase, Stripe or Sentry, or as a custom server. For services that support it, environment isolation keeps the build agent away from production data.
Can teams use their own credentials?
Yes. A team can override the organisation's Anthropic key, Claude subscription token and GitHub connection, which helps with cost and access isolation.
We've thought carefully about these areas. Some are intentional design choices, others are on our roadmap.
Each deployment registers its own GitHub App. There is no shared Bynary app to install.
MCP servers are configured separately for each project. There is no global configuration.