Viska sjóðir · AI Infrastructure

A self-updating bridge from your broker into your own AI.

Every night, the fund's raw Interactive Brokers statements become a live, queryable book of the fund — owned by you, ready for everything built on top of it.

Live · proven end-to-end Final activation pending

This arc was the fund's single largest engineering investment this month — the foundation the rest of the AI stack now stands on.

The flow

From your broker to your dashboard

One path. The broker statement comes in on the left; your AI, dashboard, and decision agents read the finished book on the right.

Source Interactive Brokers Your live brokerage account & daily statements

The bridge

Pullfetch the statement, nightly

Recordwrite each day, exactly once

Your book Live fund database

Mímir — morning briefthe AI assistant answers live portfolio questions

viska.gg dashboardpositions, NAV, allocation

Decision agentsidea → gate → decide → execute

Two triggers. A nightly schedule runs it for you automatically (live today). An on-demand "pull now" button on viska.gg is designed and coming.

The machine, part by part

Six parts, one pipeline

Each piece does one job and is kept separate from the others on purpose — so a fault in one can never corrupt your book or expose your holdings.

n8n

The conductor

Wakes every night, fetches the broker statement, and moves the data along. Carries the file but holds no keys to your database — it transports, it never writes.

Hosted on Hostinger

apply-svc

The bookkeeper

The only component allowed to write to your trading book. It re-reads each statement and records every trading day exactly once, behind a single locked gate.

Hosted on Railway

Supabase

The vault

Your own database. The trading book lives here, and the raw statements sit in private storage that the public can never read.

Your database & storage

Mastra · Mímir

The analyst

The AI agent that reads the finished book and writes your morning brief. Mastra is the engine it runs on; Mímir is the assistant you talk to.

Hosted on Railway

Cloudflare

The doorman

Guards who is allowed to open the dashboard. It checks identity at the door — auth only, never touching the data inside the pipeline.

Edge / access

viska.gg

The window

Your live dashboard — positions, NAV, allocation — and soon, the on-demand "pull now" button that runs the whole pipeline at a click.

Your web app

What it took

Why this took most of the month

The outcome is simple. Getting there meant solving real problems the broker and the data forced on us — each one quietly load-bearing.

01A two-call handshake with the broker. Request the statement, then poll for it — with retries and time-out alerts when IBKR is slow.
02Multi-day normalization. A single pull carries roughly 22 trading days that all have to land cleanly, in order.
03The write path, rebuilt three times. As real constraints surfaced, the way data reaches your database was re-engineered twice over.
04An authentication discovery. Your database signs its tokens a specific way (ES256) — found mid-build, it forced a redesign of the upload step.
05Re-run safety. Fire the pipeline twice and the book can't duplicate or corrupt a day — it records the same truth each time.
06Row-level privacy. Holdings are never publicly readable — privacy is enforced at the database itself, not bolted on.

The write path, built three times

Direct database write → Direct file upload → Server-signed upload URLs

Days of focused work across three specialist engineers and a dedicated security specialist.

The deliverable

A permanent feature in your AI stack

This is not a one-off report. A continuously-updating trading book now lives in your own database — the data foundation every other surface stands on. It updates itself, and everything built on it inherits the same single source of truth.

The morning briefMímir answers live portfolio questions each day

The live dashboardviska.gg — positions, NAV, allocation

The decision agentsidea → gate → decide → execute

What it fuels

From live data to decisions

With the book live, the same trusted numbers feed both what you see and what you can act on.

Analysis

What you can see

Daily NAV & performance over time
Allocation by theme and by metal
Concentration & single-position risk
Currency (FX) exposure across the book
Per-position profit & loss
Day-over-day change — what moved, and why

Actionables

What you can act on

Rebalancing alerts when weights drift from target
Concentration & risk-threshold triggers
A morning brief on what changed overnight
The decision agents — idea → gate → decide → execute
Live answers to portfolio questions, on demand
A foundation ready for any future AI tooling

Every surface reads the same numbers. One source of truth.

Honest status

Where it stands today

Live and proven — with the final steps to full automation in hand and clearly marked.

✓Live & proven end-to-end. A real run landed June 19 holdings — 21 positions, 5 FX balances, 3 NAV rows — straight into your book.
◐Multi-day landing. Code-complete; its production deploy is the last confirmation step.
◐On-demand "pull now" button. Designed and approved; not yet built. Today the nightly schedule does the work.
◐Nightly schedule. Armed for 22:30; pending the go-live switch.

Go deeper

The full technical map

Every claim in this page is backed by a complete, source-grounded engineering map — 11 sections and 451 line-level citations, with a confirmed-vs-pending ledger for total transparency.

Read the engineering map

Prepared for fund principals — the technical map is the engineering reference behind it.