Internal Reference Document
Shade Infrastructure
Setup Guide
Step-by-step setup for the EyeClap + NEEBA workspace on Shade — covering account creation, drive structure, team access, and Backblaze BYOS integration. Co-authored by RD White and Marlo Custodio · 50/50 Partners.
Monthly cost to start
$40 / mo
2 seats · RD + Kevin · annual billing
Platform
Shade Growth
Up to 15 seats · 150 guests · unlimited drives
Storage model
Proxy-first
1TB included · Backblaze BYOS when needed
Setup Sequence
Six Phases to Go Live
Complete these in order. Phases 1–5 are a one-time setup. Phase 6 (Backblaze) is triggered only when storage needs grow.
Set up the cheap object storage backend that will power Shade's BYOS option when you're ready to scale. Free to create now — you won't be charged until you exceed the free tier. Do this first so credentials are ready when you need them.
Sign up at backblaze.com
Create a B2 Cloud Storage account. First 10GB is free. No credit card required to start.
Create a dedicated bucket
Go to Buckets → Create Bucket. Name it something like eyeclap-shade. Note your bucket name and bucket region (e.g. us-east-005) — both required later.
Generate an Application Key
Go to Access Keys → Create Access Key. Scope it to your bucket. Enable Read and Write. Copy the Key ID and Application Key immediately — Backblaze only shows the Application Key once.
This is the master container for all EyeClap + NEEBA assets. Billing runs through EyeClap for simplicity — Marlo holds full partner access across all joint client work. The workspace is the creative infrastructure for both teams.
Sign up at shade.inc — Growth plan
Select annual billing at $20/seat/month. Start with 2 seats (RD + Kevin). Marlo joins as a full partner seat — billed at $20/mo through EyeClap and settled between partners.
Name the workspace "EyeClap + NEEBA"
The workspace name is visible to all team members and reflects the partnership equally. Both entities should feel at home in this system.
Workspace admin sits with RD for billing simplicity
Billing and technical admin consolidate under one account to keep the setup clean. This is a practical decision — Marlo's partner role and full access to joint client work is reflected in the drive structure below.
Two drives, two scopes. The EyeClap drive handles direct client relationships. The EyeClap + NEEBA drive is where Marlo operates as a full partner — complete access to all joint client work, from raw footage to final delivery. Get this structure right before files are uploaded.
Create the EyeClap direct drive
Name: EyeClap. Access: RD + Kevin. Houses EyeClap's direct client relationships — Harrelson's Own, Rayse, Cannella, Storytech, Winders Group.
Create the EyeClap + NEEBA partner drive
Name: EyeClap + NEEBA. Access: RD + Kevin + Marlo. Full partner access for Marlo across all joint clients including Bosley, Amplify, Root Evidence, Chen Institute, Heartwood, and Bloom Energy.
Create client folders inside each drive
See workspace map below for full client list. Inside each client folder, create three subfolders: _RAW · _PROJECT · _DELIVERY
Invite in the correct order. Each person should only see what they need. Clients are added as guests via published links — no seat required.
Invite Kevin Jung as a workspace member
Full access to both drives. Kevin mounts drives via ShadeFS desktop app for remote editing. Installs Shade desktop app on his machine in Cardiff.
Invite Marlo Custodio as a full partner member
Marlo receives full access to the EyeClap + NEEBA drive — all joint client folders, raw footage, project files, and deliverables. As the Shade champion and NEEBA co-lead, Marlo's access reflects his 50/50 partner role across all joint engagements.
Clients receive published links only
No client ever gets a seat or drive access. You share specific files or delivery folders via Shade's published link feature. Bosley receives links from their own separate Shade account, as before.
Run these checks before Kevin starts on Bosley. Catch any permission or connectivity issues on setup, not mid-project.
Verify each person's drive view is correct
Confirm Marlo sees the full EyeClap + NEEBA drive with all joint clients. Confirm Kevin has access to both drives. This is a quick sanity check — make sure everyone's workspace reflects their role before the first project files go in.
Kevin installs Shade desktop app + mounts a drive
Download at shade.inc/download. Kevin mounts the shared drive, opens a test clip in Premiere Pro, and scrubs playback. This validates his Cardiff connection speed for ShadeFS streaming before the Bosley project begins.
Upload Bosley test files and confirm folder structure
Move the existing Bosley footage from the current test account into EyeClap + NEEBA / Bosley / _RAW. This is Kevin's first remote editing project — "Best Decision Ever Classic · Local Office versions."
First Project Priority
The Bosley test is simultaneous proof-of-concept for ShadeFS remote editing. Kevin's first remote edit and Marlo's infrastructure validation happen on the same project — the right environment for working out any kinks before new clients enter the system.
Do not do this at launch. You have 1TB of included Shade storage at 2 seats. Connect Backblaze only when a trigger condition is met.
Trigger Conditions
When to Connect Backblaze
Approaching 80% of included storage — Shade shows usage in Settings/Usage. When proxies + project files hit ~800GB, it's time.
Deciding to store raw camera files — Kevin's Blackmagic 6K BRAW footage is large. If raw files move into Shade, connect Backblaze first.
NEEBA volume increases significantly — More joint clients means more total assets. Backblaze at $6/TB keeps costs predictable at scale.
Shade storage add-on price exceeds Backblaze — Compare Shade's per-TB add-on rate vs. $6/TB on Backblaze. BYOS wins above ~5TB overage.
In Shade: My Drives → + → BYOS Drive
Select the Video Production template. Choose Backblaze as the provider. Paste your bucket name, region, Key ID, and Application Key from Phase 1.
Configure CORS on the Backblaze bucket
Use the Backblaze CLI to run the CORS update command. This is a one-time step that allows Shade's web app to access your bucket. Full instructions at academy.shade.inc/byos/backblaze.
Upload a test file and confirm mounting works
Upload a small video file to the new BYOS drive and verify Kevin can mount and stream it from Cardiff. If streaming is slow, consider a proxy-only workflow where raws stay on Backblaze and only proxies mount via ShadeFS.
Architecture Reference
Workspace Map
Final drive and client structure. Direct EyeClap clients on the left. All joint EyeClap + NEEBA clients on the right — Marlo's home base with full partner access.
Harrelson's Own
Direct
Rayse
Direct
Cannella
Direct
Storytech
Direct
Winders Group
Direct
RD White
Full Access
Kevin Jung
Full · Mounts via ShadeFS
Bosley
Active First Project
Amplify
Joint
Root Evidence
Joint
Chen Institute
Joint
Heartwood
Joint
Bloom Energy
Joint
RD White
Full Access
Kevin Jung
Full Access
Marlo Custodio · NEEBA
Full Access · 50/50 Partner
Bosley Delivery Note
Bosley has their own separate Shade account for receiving final deliverables. Internal working files (raw, project, WIP) live in the shared drive above. Finished exports are sent to Bosley via their own account — keeping internal work invisible to the client.
File Management
Folder Convention
Use this structure inside every client folder, in both drives. Underscore prefix sorts subfolders to the top alphabetically.
_RAW
Original camera files, audio recordings, unedited source material. Kevin's Blackmagic BRAW footage goes here. Read-only after upload.
_PROJECT
Premiere Pro project files, AE compositions, DaVinci project files. This is what Kevin mounts and edits directly via ShadeFS.
_DELIVERY
Final exports ready for client delivery. Published links point here. Files leaving this folder go to the client's own Shade account or Frame.io.
File Naming — Existing Convention Carries Over
EyeClap's existing file prefix system works inside Shade exactly as documented. RD_ prefix on files sent to any editor. EL_ on files returned from Edit Lobby. GK_ from GK Ram. KJ_ from Kevin Jung. BC_ from Bo Collet. Version notation stays as V#D# (e.g. V1D1 = Version 1 Draft 1). Shade's AI search will index these prefixes and make them searchable by name, project, and client.
Budget Reference
Cost Breakdown
All figures based on confirmed Shade Growth plan pricing and Backblaze B2 pay-as-you-go rates as of April 2026.
| Line Item |
Detail |
Monthly |
| Shade — RD seat |
Growth plan · annual billing · workspace admin |
$20 |
| Shade — Kevin seat |
Growth plan · full drive access · ShadeFS mounting |
$20 |
Shade — Marlo seat partner seat |
Growth plan · full access to EyeClap + NEEBA partner drive · billed through EyeClap, settled between partners |
$20 settled between partners |
Backblaze B2 Phase 6 trigger only |
$6/TB/month · first 1TB included in Shade seats · free egress to 3× monthly storage |
$0–$30 5TB = $30/mo |
| Launch total (2 seats) |
RD + Kevin · proxy-only workflow · within included storage |
$40 / mo |
| At scale (3 seats + 10TB BYOS) |
RD + Kevin + Marlo · Backblaze BYOS connected · ~10TB total |
~$115 / mo |
Reference
Key Links & Contacts
Everything you need to set up, troubleshoot, and manage the Shade infrastructure in one place.
Shade desktop app download
Backblaze BYOS integration guide
Shade billing settings
app.shade.inc → Settings → Billing
Usage view: Settings → Usage