SampleSample tape
Sample data · no brokerage connection
One workspace file in. Allocation, performance, risk, a ledger, exports and a typed API out.
No brokerage connection · no signup · no client money
Setup service · price on request
Sample portfolio balance
$2,408,000.00
+$17,997.20 +0.75% today
One file in · six things out
Sample workspace · replace the file and every panel follows
The dashboard · sample workspace
the engineering write-up ↗Sample data throughout · no real accounts · no client money
What this one does when the feed misbehaves.
Live quotes inside an 8-second budget, with the workspace’s table behind them.
Feed resolution
Sample data, re-enacted: a quiet upstream changes what the feed reports, never what the portfolio is worth.
Resolving the feed…
One download, every chart; one bad chart, not the page.
Chart downloads
twelve separate downloads · avoided
one shared download · every chart
$0.00 counts up. A missing value is an em dash, never a gap.
Portfolio summary
sample data
A drawer on a phone, a rail on a desktop. The KPI grid reflows 4 → 2 → 1.
Sample workspace — no real accounts, no client assets. Holdings, totals and quotes: one file.
The inventory, and the policy behind it.
No brokerage connection, no client money. Custody and KYC are a different product.
In-memory
Resets on a cold start. Stripe’s Checkout Session record is the durable copy.
None
No sign-up, sign-in, user session or user record.
Server-side only
The payment key stays on the server; the price feed carries no key.
One key
tellerswindow:welcome-dismissed — one flag, workspace-scoped.
None
Only Stripe’s checkout page sets its own.
Two hosts at most
CoinGecko for a quote on four symbols; Stripe only for a checkout.
Stripe, where configured
The card form is Stripe’s page — no card field here. A purchase is recorded only after Stripe’s signature checks out.
None claimed
No SOC 2, no ISO 27001, no pen test, no insurance.
Firewalled twice: an 8-second abort on the server, and a browser whose only script connection is this origin. Checkout is a navigation to Stripe, not a connection.
If something here reads like marketing, that is a bug.
Ask something elseA portfolio dashboard. One file — positions, quotes, a ledger — becomes allocation, performance, risk, exports and an API.
Sample data, labelled wherever a number appears. The live call covers four symbols inside an 8-second abort, and the page names the source.
Yes. Replace the two files and rebuild; every surface reads them. Settings’ Data panel names and downloads both.
The live feed timed out, was rate-limited or sent something unusable, so the quote came from the workspace’s own table — and the page said so.
No. There is no Plaid, Yodlee, OAuth or exchange key in the build, so there is no path to a real account.
No, and it could not be: no brokerage accounts, no client records, no assets — nothing to insure, secure or audit.
Yes — holdings as CSV, JSON or HTML, any chart as a PNG, the ledger as CSV, and the Data panel downloads both files.
No. No analytics, no pixel, no tag. One flag in your browser records that you closed the welcome panel.
The dashboard is free, and pointing it at your own data is a file replacement you can do yourself. What can be paid for is having that done for you: the setup service, priced by the deployment.
What it does today, and the edges it does not cross.
Have it done for you
Your two workspace files in place of the sample’s, rebuilt and checked.
Checking whether payment is switched on…
Not a backlog and not a promise — this is what the product does not do.
One workspace file in, one live price call that names its branch, and a chart that never renders blank. The dashboard is free; the setup service costs money.