|
SACRED STUDIOS
|
Sacred OS · Launch Readiness · 2026-06-18
The Portal is a fortress. And it's ready to ship.
We didn't just finish the client portal. We sent 14 agents to break into it — every door, every endpoint, every tenant boundary. They got in 7 ways.
We sealed all 7, then re-attacked each one to prove it's shut. Here's the receipt.
|
|
7 / 7
break-ins sealed |
|
14
attack agents run |
|
0
holes left open |
|
What the red-team found — and what we did
Every item below was reproduced live, fixed, then re-tested.
|
|
CRITICAL · CROSS-TENANT
Staff endpoints trusted any logged-in account
A client's stray internal login could have read or edited any tenant's billing & data. Sealed: all 4 internal endpoints now verify Sacred-staff identity; the stray account was deleted. |
|
CRITICAL · ALERT TAMPERING
The open internet could inject — or silence — our ops alarms
Anyone could fake alerts or mute a real outage warning. Sealed: the alarm channel now requires a secret only our monitors hold; verified an anonymous write is rejected. |
|
HIGH · THE PAYWALL
An unpaid client could still pull their finished work
The "pay to unlock" gate covered 5 tables but not the results & content feeds. Sealed: the gate now wraps all 17 data feeds + the roadmap. Verified: a locked client now reads zero withheld rows. |
|
HIGH · CLICKJACKING
The portal could be framed by a malicious site
No anti-framing headers were live. Sealed: six security headers now ship on every response (X-Frame-Options, CSP, HSTS…). Verified live over HTTPS. |
|
HIGH · SIGN-UP ABUSE
Strangers could create empty accounts
Self-signup was open (blast radius was capped — those accounts see nothing). Needs you (60 sec): one toggle in the Supabase dashboard. Steps below. The rogue test accounts are already deleted. |
|
What held under fire 🛡️
Attacked directly with forged tokens, wrong-tenant reads, and anonymous writes — and didn't budge:
| ✓ Tenant isolation — every wrong-tenant & anonymous read returns empty |
| ✓ Un-forgeable identity — a client's tenant is derived server-side, can't be spoofed |
| ✓ Delete-my-account — rejects forged tokens, only ever deletes the caller's own access |
| ✓ Secrets locked — no service key or secret is reachable from the shipped app |
| ✓ File storage — public can read, but anonymous uploads are blocked (403) |
| ✓ Notifications — fire exactly once, OTP login is rate-limited, native CORS locked |
|
It's not a web page anymore. It's an app.
|
📦 Native iOS shell, built
Wrapped with Capacitor, icons & splash generated, external links open cleanly in-app. Bundle is synced & ready for Xcode. |
|
🔔 Real phone push, wired
Lock-screen notifications that open the app — the trigger chain is live and fires once. Lights up the moment a device subscribes. |
|
|
🛟 App-Store essentials, in
Delete-account, privacy policy, self-hosted SDK (no CDN), offline shell — every Apple checklist item buildable today is done. |
|
🧭 Command Center, calmer
Per-client view condensed 8 tabs → 6, Bigin retired, onboarding now captures GA4/Retell/Meta keys (skippable). |
|
Your move — 3 steps to live on your phone
|
STEP 1 · 60 SECONDS · the one security toggle
Supabase → project sacred-portal → Authentication → Sign In / Providers → turn OFF "Allow new users to sign up". (Client invites still work — this only blocks strangers.)
STEP 2 · OPEN IN XCODE & RUN ON YOUR iPHONE
1. Open ~/sacred-portal-app/ios/App/App.xcworkspace in Xcode.
2. Plug in your iPhone, pick it in the device dropdown (top bar).
3. Select the App target → Signing & Capabilities → choose your Apple ID team (auto-signing).
4. Press ▶ Run. The Sacred app installs on your phone & opens. Sign in with your portal email + code — that's the real thing in your hand.
STEP 3 · SHIP TO THE APP STORE (when Apple approves you)
In Xcode: Product → Archive → Distribute App → App Store Connect. Then in App Store Connect, fill the listing (icon's ready), attach the privacy policy URL, and submit for review. The only thing between us and the store is your Developer Program approval — everything on our side is done.
|
|
Is it all connected? Yes.
Every pipe is built and traced end-to-end: daily metrics, SEO/GBP/reviews, notifications→push, lead capture, and deal-won→onboarding all flow into the portal automatically. Live data is already streaming for O's Concrete and Pinnacle Wash. The remaining feeds (D Scapes & DMI, plus GA4/Retell/Meta) are wired and waiting on their data sources & API keys — they light up the instant those connect, no new build required.
|
|
Hardened. Connected. Ready.
Let's win. 🚀
|
|
Sacred Studios — Not an agency. A system. portal.sacredstudios.ai · command.sacredstudios.ai
|
|