UltimariiGetting set up

What you need to run Ultimarii

Ultimarii runs in your web browser. There’s nothing to install. This page covers what your computer and connection need so it runs well — and lets you test both.

Checking this browser…

One moment.

Upload test

Sends a 24 MB test file to Ultimarii’s storage the same way the app uploads your documents, then deletes it automatically. Nothing from your computer is sent — the test file is random data generated in your browser. This is the check that most often explains “uploads don’t work at the office”.

Test file size

Your browser

BestMicrosoft Edge or Google ChromeWhatever version your IT team keeps updated. This is what we test against first.

Also fineSafari 17 or newer, Firefox 128 or newer

Won't workInternet Explorer, or any browser more than a couple of years oldIncluding Firefox ESR 115, which is sometimes still installed on managed work computers. If pages look broken or overlapping, this is usually why.

Not sure what you’re running?The panel at the top of this page has already checked the browser you’re reading this in. If it’s showing a warning, that’s worth sorting out before you start.

Your computer

Works8 GB of memory, any laptop from roughly 2018 onwardsEveryday use is fine. Very large PDFs will feel slow.

Comfortable16 GB of memory, a machine from 2021 or later

Operating systemWindows 11, or macOS 13 and laterWindows 10 is no longer receiving security updates, so it isn’t supported.

Not supportedPhones and tabletsUltimarii puts a document and a conversation side by side, which needs a proper screen. Use a laptop or desktop.

Your screen

Minimum1366 × 768

Recommended1920 × 1080 or largerYou’ll be reading a document and a conversation at the same time. More width genuinely helps — below about 1440 pixels wide things start to feel cramped.

Your internet connection

Minimum10 Mbps down, 5 Mbps up

Recommended50 Mbps down, 25 Mbps up

Wi-FiFine — a stable connection matters more than a fast oneUltimarii keeps a live connection open to show new results as they arrive. A connection that keeps dropping is more disruptive than a slow one.

Uploading takes as long as it takes.Your upload speed is usually much lower than your download speed. A 300 MB PDF takes around 8 minutes on a 5 Mbps connection, or about a minute and a half on 25 Mbps. If you’re uploading a big batch, start it and carry on with something else — it hasn’t frozen.

What you can upload

File typesPDF, Word (.docx), PowerPoint (.pptx)

Size limit300 MB per PDF, 50 MB per Word or PowerPoint file

At onceUp to 100 files in a single batch

If it’s slow or something won’t load

Most problems on a work computer aren’t your computer — they’re a setting on the company network. Try these first, in order:

1Reload the page. If you’ve had the tab open a long time, this fixes a lot.
2Check the two panels at the top of this page — the browser check and the upload test.
3Try the same thing on a home or mobile connection. If it works there but not at the office, it’s a network setting — send your IT team the message below.
4Still stuck? Contact us, and mention whether step 3 made a difference and what the upload test said. It tells us where to look immediately.

Message for your IT team

If Ultimarii works outside the office but not on it, copy this and send it to whoever manages your network. It’s written for them, and it names the specific settings involved.

Ready to send

Hello,

We use a web application called Ultimarii, and it works correctly outside our network but not on it. It has some specific requirements that corporate proxies and TLS-inspection appliances often interfere with. Could you check the following for our tenant hostname on *.ultimarii.app?

1. HTTP/2 must be preserved end-to-end. Some inspection appliances terminate HTTP/2 and re-originate to the client as HTTP/1.1. The application opens 15-20 concurrent long-lived connections per session, so under HTTP/1.1's six-connection-per-origin limit it stalls with no error shown.

2. Long-lived GET responses must not be buffered. The application streams results progressively; a proxy that buffers the full response before forwarding makes it appear frozen.

3. Idle/read timeout should be at least 60 seconds (120 preferred) on any proxy, VPN concentrator or firewall in the path. Shorter timeouts cause connections to be cut and re-established in a loop.

4. Document uploads go directly from the browser to Azure Blob Storage over HTTPS, in 8 MB blocks. Please confirm that:
   - outbound HTTPS to Azure Storage is permitted
   - if internal DNS hosts a privatelink.blob.core.windows.net zone, it does not shadow the public name we use
   - no upload size or request body limit below ~10 MB applies to these requests

5. These destinations need to be reachable over HTTPS:
   - our tenant hostname on ultimarii.app
   - *.clerk.com, *.clerk.accounts.dev, api.clerk.com  (sign-in)
   - challenges.cloudflare.com  (sign-in verification)
   - *.blob.core.windows.net  (document upload and viewing)
   - api.electric-sql.cloud  (live data updates)
   - posthog.ultimarii.app, *.ingest.us.sentry.io  (diagnostics)
   - *.appcues.com, *.appcues.net  (in-app guidance)
   - fonts.googleapis.com, fonts.gstatic.com  (fonts)
   - res.cdn.office.net, teams.microsoft.com, *.cloud.microsoft, *.office.com  (if we use the Microsoft Teams tab)

6. WebAssembly and web workers created from blob: URLs must not be disabled by browser policy - the PDF viewer needs both.

Note: WebSockets are not required. Everything runs over ordinary HTTPS.

Thank you.