Pre-launch · not yet generally available

Eight tools. Eight logins. 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.

What pre-launch means here
FreshNow is not open to the public. There is no consumer sign-up, no plan you can buy today, and nothing on this page you can log into. Everything below describes software that exists and is in active development, and each product states its own stage. If a claim on this site is not accurate, write to hello@freshnow.net and we will correct it.
Opening first

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.

Try it

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.

Simulated
Pick a request
Pick a request
The suite

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.

fresh·orbitIn development

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 →
fresh·orbit IT service desk, running in development with a made-up company.
fresh·umbraIn development

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 →
fresh·umbra, run locally with made-up people. The answer’s wording is scripted for the screenshot; the lookups and the draft run through the real code.
fresh·huddleIn development

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 →
fresh·huddle as it runs today. The team and messages are made up; the huddle is a real call.
fresh·beaconIn development

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 →
fresh·beacon, run locally against a throwaway database with made-up incidents.
fresh·prismIn development

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 →
fresh·prism with made-up documents. The permission check runs on the server, so it doesn’t show on screen.
fresh·ledgerIn development

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 →
fresh·ledger with a made-up company and made-up merchants.

All eight at a glance

fresh·orbit
CRM · support · operations
In development
Opening first: the IT service desk
Every account, deal and work order in one place.

The annoyanceThe customer’s history lives in three tools, and none of them agree.

The largest product in the suite. Sales pipeline and forecasting, a full support desk, customer success health scoring, plus manufacturing, inventory and distributor modules for industrial teams.
Sales & pipelineSupport deskCustomer successManufacturing
Read the detail →
fresh·beacon
Incident response
In development
The signal the moment something breaks.

The annoyanceFinding out about the outage from a customer.

A four-level severity scale and a two-way CRM link: a critical account in the CRM raises an incident, and resolving it publishes back. On-call scheduling, war rooms, and an affected-customers panel that surfaces which accounts an incident touches are all built.
On-call & escalationSEV1–SEV4War roomsPostmortems
Read the detail →
fresh·prism
Enterprise search
In development
One query, refracted through the sources you connect.

The annoyanceKnowing the answer is in a document somewhere, and searching four places to find it.

Search over a connected source, with every result filtered against the permissions captured at ingest so search never becomes a way around access control. Google Drive is the connector that exists today; searching across the rest of the suite and other sources is planned.
Google Drive connectorPermission-awareTenant-scopedCross-product search — planned
Read the detail →
fresh·huddle
Messaging · meetings
In development
Opening first
Where your people gather.

The annoyanceA ping at 9 p.m. that could have waited until morning.

Chat and meetings in one place: channels, threads and DMs, huddles with audio, video and screen share, and meeting invites that repeat and go on your calendar. Built and in testing; not yet open to customers.
Channels & DMsHuddles: audio, video, screen shareMeeting invitesDesktop app
Read the detail →
fresh·ledger
Finance · accounting
In development
The books, kept where the work happens.

The annoyanceLogging into a separate system to see whether an invoice got paid.

Double-entry accounting for the suite. The Plaid bank-sync and AI categorization pipeline is connected to a real bank and runs against our own books; wiring invoices, purchase orders and journal entries into one operational chain is planned.
Double-entryBank syncAI categorizationInvoicing — planned
Read the detail →
fresh·umbra
IT helpdesk agent
In development
Opening first
An IT helpdesk agent that can only do what your policy allows.

The annoyanceThe same password reset five times a day, with no record of how anyone checked it was really them.

An AI agent for the routine IT tickets — password resets, MFA re-enrollment, access requests, joiners and leavers — built so a policy check comes before every action and a named person stands behind every change.
Policy before actionVerified resetsApprovals in TeamsHaloPSA
Read the detail →
fresh·guard
Security control plane
In development
One security control plane the products wired to it share.

The annoyanceSecurity settings that drift apart, one product at a time.

DLP, malware scanning, sign-in risk enforcement and an append-only audit log — implemented once as a control plane the products wired to it share, rather than rebuilt separately in each.
DLPMalware scanningSign-in riskUnified audit
Read the detail →
fresh·anchor
Customer identity
In development
The trusted point your users authenticate through.

The annoyanceAnother app, another password your users will forget.

Customer-facing identity: the login your end users see, separate from the internal directory your staff use.
Customer IdPSSO federationSelf-service
Read the detail →
Release status

Where each product actually is

We would rather tell you a product is unfinished than let you assume it is ready.

Early access0 products
Nothing at this stage
Working software, ready for the first companies we onboard. Not self-serve and not generally available.
In development8 products
fresh·orbit · fresh·beacon · fresh·prism · fresh·huddle · fresh·ledger · fresh·umbra · fresh·guard · fresh·anchor
Being built now. Design settled, not ready for customers.
Planned0 products
Nothing at this stage
A committed direction with no production code and no date.
The security layer

Security 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.

One security control plane
one policy surface for the products Guard covers rather than per-product security settings that drift apart.
Enforced at the action
upload scans, export checks and sign-in risk decisions happen inline, not in a nightly report.
One audit trail
security decisions are written to a single append-only audit log rather than scattered per-product logs.
Threat detection
Planned — detection of login bursts, off-hours access, bulk export, privilege escalation, API abuse and geographic anomalies is not built today.
Hosted on Amazon Web Services
Infrastructure, storage and content delivery all run on AWS. Data-residency requirements are worth raising before an evaluation, not during procurement.
Who we are

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.

Legal entityFresh Now LLC
FormedMassachusetts, United States · 2026
Domainfreshnow.net
StagePre-launch · preparing for first customers
InfrastructureAmazon Web Services
Trust & transparency

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.

Email sales directly