HyphaOps™ Client

Lesson 1

Why use a client?

The portal (browser) is for shared work: log in, keep compliance records, use the same system as your team. That is multi-user cloud software.

A client is for work that must happen on your machine: a private local database, offline copies, and handoff to Excel, Access, scripts, or backups. The website is not wrong — it solves a different problem.

Rule of thumb: if you only need screens and forms, stay in the portal. If you need data on your box next to other desktop tools, use a client.

Lesson 2

What HyphaOps Client is (and is not)

It is not a second portal UI. There is no full dashboard to “live in.” You open a terminal and run short commands.

It does three jobs:

1. Application integration — talk to the HyphaOps / portal API (reach the cloud application).
2. Database integration — write what you pulled into a local SQLite file on your computer.
3. Import / export JSON — move data in and out as files so other systems can use them offline.

Farm and ops pattern: portal for compliance and shared records; local tools for day-to-day integration. The cloud remains the shared source of truth. The client is the local integrator.

This software installs and runs on your computer. The portal is the website you use in a browser.

Lesson 3

Picture the data path

Read left to right. Arrows mean “you run a command that moves data that way.”

Portal (cloud)          Client (your PC)           Your other tools
─────────────          ─────────────────          ────────────────
accounts, lots,   →    sync / ping / export   →   Excel, Access,
catalog, APIs          local SQLite               scripts, backups

• ping — “Can I reach the portal?”
• sync — “Pull catalog data into my local database.”
• export — “Write a JSON file I can open elsewhere.”