
- TNAADO
- Technology
- Technology portfolio
S.00 Technology portfolio
What we shipped.
Camera work is at the media portfolio →
S.01 Applications
Our apps.
01 From brief to the App Store
Swift one app, brief to store
The briefOne screen. A person opens it, sees what is near them, and picks. Nothing else on the screen.
- BriefWhat it is for, before anything is drawn.
- WireframeEvery screen drawn before a line of code.
- BuiltNative, on a device, with your content wired in.
- On the storeScreenshots, listing, review, live.
TNAADO Labs is our sister firm in Miami. Same engineers, separate company. About Labs →
S.02 Sites and stores
Sites and stores.
Client work and our own brands sit side by side here, and every card says which: a client project was commissioned and paid for, a brand or venture is ours to run. Dream Daley is this firm under another name, not an outside client.
S.03 The firm's own systems
The software we run on.
We run this firm on software we wrote. Our bookings, our kit and our payroll sit inside the same queues, registers and ledgers we build for clients. Over 30 live deployments.
Decision queues
Work is held until someone with authority decides, and the decision is recorded.
Newsroom CMS
Article, journal entry or episode: one review queue, one compliance
sign-off. Everything the newsroom publishes is filed through it.
Review queue
-
Socials
Accounts connected through their official APIs, with publishing, scheduling and approvals.
Publishing queue
Socials, publishing queue. One row per destination rather than per post, so a post going to four accounts is four jobs and three can be ticked off while the fourth waits.
Socials, the month ahead. Every planned post on its day, with where it is going and whether it has been approved.
Socials, the brand list. Every brand the firm posts for, grouped under the organisation that owns it. -
Dispatch Live Marketplace
Footage watched as it arrives, graded, and released only on a decision.
Footage board
Dispatch Live, footage board. Capture arrives as pending and pending is invisible, so nothing reaches the public map or a buyer until somebody presses release.
Dispatch Live, one decision. Withholding a clip asks for the reason first, and the reason stays on the record with the name of whoever released or held it.
Dispatch Live, complaints. Somebody objects to a clip, a person decides, and the outcome is written down next to it. -
App Management Portals
The operator's side of each app, built to one shared pattern.
Reports queue
App portals, reports. Each reported clip shows how many people reported it and why, who posted it, and how many strikes that account already holds. Three active strikes bans it automatically.
App portals, support. Every message from a user carries the app version they were on, so a fault can be matched to a release.
App portals, the record. Every action, who took it and why, in a log nobody can edit afterwards. -
Labs Admin Backend
The accounts, content and change records behind the Labs products.
Support queue
Labs admin, support. Every request carries a category, a priority and a state of open, in progress, resolved or closed, and the list filters on all three.
Registers
Every unit, booking and ticket carries a state you can look up before promising it.
Equip
A QR label on every unit opens its record: status, condition,
location, parts. Every camera on a shoot is booked out of it.
Inventory
-
The Shoot
Productions booked, crew and models paid, equipment assigned, payroll run.
Production board
The Shoot, production board. Every shoot across the team, split into upcoming, in progress and wrapped, each card carrying its client, call time, location, crew count and how many of its tasks are done.
The Shoot, one day. Call time, wrap time, location, brief and budget on one screen, with crew, gear, hours and payments a tab away.
The Shoot, crew. Who is available, what they do, and how they are paid. -
Events and Ticketing
A QR ticket on every sale, and a door scanner at the event that checks it.
Events
Events, the event list. Each event with its date, venue, price range and how many tickets have gone.
Events, one event. Money taken, seats left, and how each ticket type is selling.
Events, orders. Every sale with the buyer, the amount and whether the payment actually went through.
Events, the door. A ticket is scanned or typed in and the count updates as people come through. -
Photo Licensing Store
Public previews are watermarked; the clean original sits in private storage behind a signed link.
Licensing
Photo store, one photograph. The preview is watermarked and the clean file sits behind the payment.
Photo store, the gallery. Photographs grouped by subject with a price on each, and a watermark over every preview.
Photo store, uploading. The original goes into private storage and the watermarked preview is made for you.
Photo store, after payment. The buyer gets a link to the clean file, and that link expires in an hour.
Accounts and ledgers
Who someone is, what they are owed, and what has actually been paid.
Revenue and cost from every property in one ledger. Billing and payroll run off it.
No screen on this one: both captures publish the firm's own revenue and payroll, and neither belongs on a page a client reads.
-
Client Portal
A client's projects, the shoots inside them, the budget agreed and the invoices raised.
Projects
Client portal, projects. Each project opens into the individual shoots inside it, with the date, the studio or location, the state it has reached and the deliverables and budget agreed for each one.
Client portal, the front page. A client signs in and sees their work, their bills, their card on file and their own company details.
Client portal, invoices. What is paid, what is due and what is late, in one list.
Client portal, one invoice. Line by line with tax shown, printable, and payable from the same screen. -
Reporter Portal
What each accepted pickup earned.
Earnings
Reporter portal, earnings. Commission accrued since the last payout, what is cleared and queued, what is still in review hold, and the date of the next run. A reporter only ever sees their own figures.
Reporter portal, recent pickups. Every accepted item with what it sold for and what the reporter earned from it.
Reporter portal, getting paid. Bank details and tax go to Stripe, never to us, and payouts run every second Friday.
Reporter portal, signing in. A one time link to the address on the account, so there is no password to lose. -
Merch Store Admin
Orders, from checkout to the print partner to the door.
One order
Merch admin, one order. Paid, then refused three times by the print partner because the colourway was unavailable in that region. The record says so in red instead of going quiet.
Merch admin, orders. Canadian and American takings side by side, with the orders that need a human pinned to the top.
Merch admin, the front page. Orders, revenue, traffic and live discount codes on one screen. -
TNAADO Portal
One identity, one workspace and one billing relationship behind every module a business uses.
Workspace
TNAADO Portal, the workspace. Identity, billing and data are shared across every module, so somebody signs in once and works everywhere.
TNAADO Portal, modules. Eleven modules on one account, grouped by what they are for.
TNAADO Portal, permissions. A job title is a list of ticked capabilities, so what somebody can do is written down rather than assumed.
TNAADO Portal, the team. Invite by email, set the role, and see who has accepted and who has not.
TNAADO Portal, signing in. Google, Apple, an email and password, or a link sent to your inbox. -
Reader Portal
Sign-in with Google or Apple. No password in the product.
Membership
Reader portal, membership. A paying member sees the tier they are on, that it is ad free, when it renews, and one button through to the billing portal to change or cancel it.
Reader portal, the account. A free reader sees the tier they are on and what supporting the newsroom would change.
Reader portal, signing in. Google or Apple only. There is no password in the product to lose.
Reader portal, the wrong door. A business account that lands here is told so and sent to the client portal instead.
The workshop
Behind all of it, tooling with no customer. Vault and Workflow Systems holds every credential in one controlled store and the firm's procedures as workflows. TNAADO Command runs AI agents on one codebase, each with its own context. Command Central calls, records and files the meetings. Applied AI Research is an internal programme. None of it ships to a client; it is how the rest gets built.
How they work
01 Who can see which rows
Postgres select * from projects
create policy projects_own on projects for select using (owner = auth.uid() or public.is_staff());
0 rows: the policy denied every row to this caller.
6 of 6 rows returned · every row is in the table; the policy decides which of them a caller gets
Press a caller. The rule lives in the database, so it holds even when the app asks the wrong question.
02 A payment that fails
Stripe PaymentIntent
attached
action
- payment_intent.created: created
- payment_method.attached: requires_confirmation
- payment_intent.requires_action. 3-D Secure
- payment_intent.payment_failed: card_declined
- payment_method.attached: retry
- charge.pending: processing
- payment_intent.succeeded: succeeded
- event
- payment_intent.succeeded
- CAD
- status
- succeeded
- live
This demo declines on purpose, then retries.
03 Work that runs with nobody there
Server one day
24:00 · a full day, start to finish
Nobody opens a laptop for any of this.
Book the call
Tell us which one above is closest, and we will scope yours.
Thirty minutes with the engineer who would build it.










