Credential Provisioning
AXIS ASI TRADER — Admin → Credentials
Security Doctrine: Credential values are stored server-side as references only. They are never returned to the browser after storage, never logged, never included in AI context, and never transmitted in client bundles. Rotate any key immediately upon suspected exposure. New broker connections default to READ ONLY — trade permission requires deliberate elevation.
Database
0/1 configuredPrimary database, authentication, and row-level security. Required before any persistent state.
Service role key must never appear in client bundles or logs.
Anon key is safe for browser use — RLS enforces tenant isolation.
Rotate service role key immediately on any suspected exposure.
Rotation Policy
Manual — rotate anon key quarterly, service role key on security events
Never rotated
Credential Fields
Found in Supabase Dashboard → Settings → API
NEXT_PUBLIC_SUPABASE_URL
Safe for browser — enforces RLS policies
NEXT_PUBLIC_SUPABASE_ANON_KEY
SERVER ONLY — bypasses RLS. Never expose to browser.
SUPABASE_SERVICE_ROLE_KEY
Environment Variable Keys
NEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_ANON_KEYSUPABASE_SERVICE_ROLE_KEYSet these in your .env file. Secret values are never returned to the browser after storage.
Stripe
0/1 configuredAI Providers
0/4 configuredBrokers
0/1 configuredTrading Cloud
0/1 configuredConfiguration State Guide
Credentials are stored as server-side references — values are never returned to the browser after initial save.
Secret fields (marked SECRET) are write-only from this interface. Existing values are shown as masked placeholders.
Rotation creates a new credential version. The old version is revoked after verification of the new one.
Verification tests the credential against the provider without exposing the value.