Mission controlfor small IT teams.
Eight tools, eight logins, and none of them talk to each other. We’re building the one place they meet. It starts with the people who run IT: a service desk, an IT helpdesk agent that asks before it acts, and team chat. Those three open first.
fresh·huddle, the trailer
Real screens from fresh·huddle as it runs in development, with a made-up team. The music was written for this trailer. fresh·huddle is not released yet.
What the trailer says and shows
Paying too much for chat and meetings? Per seat. Per add-on. Every month. You want enterprise power, without the enterprise price. A countdown runs out and a cartoon rocket lifts off. Then fresh·huddle: chat, calls, meetings and guests in one place. The screens that follow show channels, threads and @mentions; huddles with voice, video and screen sharing; scheduled and repeating meetings with invites, RSVPs, calendar files and a Join button; guests who join with a link and wait until someone admits them; chat inside the call, saved afterwards; busy, away and do not disturb; admin switches for each feature and an audit log; and light or dark. It closes on “Enterprise impact. Not the enterprise price.” and “fresh·huddle. Coming soon.”, then a crescent eye opens in the dark above “Someone’s coming aboard.”
For the people who run IT
Three products are closest to early access. They are for the people who keep a small company’s IT running, in-house or at a managed service provider.
In our staging environment, fresh·umbra already drafts tickets into the fresh·orbit service desk. A person checks each draft and clicks Create.
Watch a request go through the trust layer
A scripted walkthrough. Nothing here calls an AI model or touches a real directory — it shows the order of checks the agent is being built to follow. Pick a request, then play the person who decides.
Eight products, one system
Every card opens a detail view: what the product does today, what it does not do yet, and where it sits in the release plan. Nothing here links to a page that does not exist.
These are real screens from each app as it runs in development, filled with made-up companies and people. Nothing here is released yet; each row says where the product stands.
An IT service desk that sees the device and the known error
The fresh·orbit IT service desk keeps the ticket, the person, their laptop and any known problem on one screen, with the SLA clock in view.
- A ticket queue with each ticket’s SLA clock
- Known errors linked to tickets, with the workaround inline
- The requester’s device and its patch status on the ticket
- Public replies and internal notes on one timeline
Tickets, SLA tracking, problem records and a directory connector work. The interface is written and not yet released.
More on fresh·orbit →An IT agent that looks things up, drafts, and waits for you
Ask fresh·umbra about a user and it checks the directory, explains what it found and drafts a ticket. Nothing is created until a person clicks Create.
- Looks up accounts and sign-in methods in a Microsoft Entra directory
- Drafts a ticket for the fresh·orbit service desk, raised in your name
- Risky changes, like a password reset, wait for a second admin
- Every check and decision lands in an audit log
Runs end to end in our staging environment against a test directory. No company uses it yet.
More on fresh·umbra →Chat, DMs and meetings in one place
Channels, direct messages and group DMs, huddles with video and screen share, and meeting invites that repeat. A mention waits until the person is working.
- Direct messages and group DMs, with a huddle one click away
- Meeting invites, once or repeating, with Going, Maybe or No and Add to calendar
- Huddles with audio, video and screen share
- Mentions wait for working hours or Do not disturb; urgent ones get through
Each of these is verified live in our own deployment. Not yet open to customers.
More on fresh·huddle →A war room for every incident
fresh·beacon gives each incident a severity, a commander and one timeline, with the alerts that set it off grouped alongside.
- Four severity levels, SEV1 to SEV4
- Internal and public notes on one timeline
- Repeated alerts grouped, with a count
- On-call schedules and escalation policies
In development alongside fresh·orbit. Not yet available to customers.
More on fresh·beacon →Search that shows only what you’re allowed to see
fresh·prism searches a connected Google Drive and checks every result against that document’s permissions before it shows it.
- A Google Drive connector, with OAuth tokens encrypted at rest
- Results filtered against each document’s permissions
- Each company’s index kept separate
Google Drive is the one connector today. Searching the rest of the suite and AI answers are not switched on yet.
More on fresh·prism →Bank transactions, categorized before you look
fresh·ledger suggests an account for each bank transaction, with a confidence score, and flags anything unusual. You override or ignore it before anything is posted.
- A suggested account and a confidence score on every transaction
- Unusual transactions flagged for a second look
- A double-entry ledger underneath, balanced in the database
The newest product. Posting categorized transactions to the ledger, invoices and purchase orders are not built yet.
More on fresh·ledger →The full mission
Where each product stands today.
Run an MSP?Fly with us
We are looking for a small number of managed service providers to run the agent with one or two of their own clients first, and to tell us where it is wrong. Partners keep the client relationship and set the client’s price. Tell us about your practice and we will reply from a real mailbox.
Join the MSP pilotSecurity isn't a bolt-on. It's the spine.
fresh·guard is one control plane the products wired to it mount, not a per-product feature. The same policy engine decides an upload scan in one product and an export block in another, and their decisions land in one audit trail.
Fresh Now LLC
We build operational software for small and mid-sized industrial companies — manufacturers, distributors, and the service teams supporting them. The suite grew out of one support-desk product and expanded because the same question came up in every conversation we had: why does every tool need its own login, its own permissions model, and its own idea of what an account is.
How we handle what you send us
The only thing this site collects is an early-access request: your name, work email, company, which products interest you and what kind of team you are. It goes to Formspree, a third-party form processor, and on to our sales inbox. We name it because you should know where your details go before you type them.
Want early access?
We onboard a few companies at a time and talk to each one first. Tell us where to reach you and what you are trying to fix.