ACCOUNT DIRECTORY
Not connected
Connect account data to view registered users.
View users →AUXE / PRIVATE WORKSPACE
Owner desk
01 / THE BIG PICTURE
A clear view of what’s recorded.
Lifetime cash entries in USD. Missing connections are shown below.
TESTER FEEDBACK
Checking…
Bugs, suggestions and feedback from the app.
Open private inbox →WHAT PEOPLE ARE DOING / ALL TIME AND THIS WEEK
Checking…
RECORDED AI USAGE / ESTIMATE
Checking…
Reading the brain’s usage ledger…
Separate from cash. It is not added to your expenses.
What this covers
Manage connections →02 / MONEY
Every recorded payment.
Record actual payments, bills and refunds here. AI estimates and unused generation credits stay separate. Payment and vendor billing feeds are not connected yet.
Scroll across the table for amounts and entry actions.
| Date / source | Category | Type | Amount | Actions |
|---|
Income is after customer refunds. Spending is after vendor refunds. Net is recorded income minus recorded spending, not an accounting profit statement.
03 / USERS & DATA
The people testing auxe.
Tap View data on anyone to see their photos, every food they logged, their workouts, their coach conversation and their body numbers. Only what has synced to their account shows. Guest use cannot be seen here.
04 / FOODS
What auxe has learned.
When a barcode is not in any database, the person scans the package’s label and auxe keeps it for everyone. Below: every food learned that way, and the barcodes still missing.
Learned from label scans
| Food / barcode | Calories | Serving | Scans | Status |
|---|
Barcodes nobody had
The most-scanned first. Scanning one of these packages’ labels teaches it to auxe.
| Barcode / name if known | Times scanned | First | Last |
|---|
05 / CONNECTIONS
Know where each number comes from.
A connection being configured is not proof that it is working. Refresh reads the available services again.
Account-data connection setup
Users, activity and synced records need one private Supabase key on the Forge server. Three steps, once:
- In Supabase, open your project, then Project Settings, then API Keys. Copy the secret key (it starts with
sb_secret_). Never the publishable one. - In Railway, open the Forge service (the one serving auxe.org), then Variables, then New Variable. Name it
AUXE_SUPABASE_SECRET_KEYand paste the key as the value. - Let Railway redeploy (about two minutes), then press Refresh here. Account data turns Configured.
Keep the key out of the app, source code and chat.
The owner login is the same verified account used for the feedback inbox. This dashboard can only read account data; it cannot reset or edit a tester’s progress.
Open Supabase ↗ · Open Railway ↗Money and billing coverage
Add hosting, AI bills, generation purchases, tools and incoming payments to the cash ledger using the amount you actually paid or received. Export the ledger whenever you need a copy.
Stripe or another payment provider is not connected. Railway, Higgsfield and other vendor invoices are not imported automatically. The shared brain’s estimated usage is shown separately, so entering an AI bill does not double-count that estimate.