Why we exist
We build small Microsoft-native apps that do day-to-day IT and compliance work inside your own Microsoft tenant, so you never hand us your data.
The problem we saw
Many software vendors ask for a copy of your data to provide one function. That copy sits in a system you do not control, under terms the vendor can change, and it is a place your data can leave from: a breach, an insider’s export or a sale of the company.
You take on a risk with every vendor you add. We build our apps so that the risk stays with you, inside the tenant where your own controls already apply.
How the apps work
Each statement here is written from the code and cited in our repository
Your data stays in your tenant
The apps read and write your data in your own Microsoft 365 tenant, from your browser, under your sign-in. An app’s server answers a short list of requests: the tools menu, a bug report you choose to send, and a health check. The Portal’s server also answers a billing check, and Bid’s serves public federal notices. None of them receives your tenant’s data.
Billing is what we hold
What we hold about you is billing, nothing beyond what Stripe, our payment processor, holds: who pays us, for which apps, and how much. What is in your tenant is not part of it.
You sign in with Microsoft
You sign in with your Microsoft Entra ID account. We issue no password of our own, so there is no second password to phish or to reset. When your admin blocks a person’s sign-in in Entra ID, Microsoft stops issuing that person new tokens for our apps; a token already issued works until it expires.
An app can do only what both allow
When you use an app in your browser, it acts as you. Microsoft lets it do only what your admin consented to for that app and what you yourself are allowed to do, so the narrower of the two applies.
The session lives in your browser
Your sign-in token lives in that browser tab and is gone when the tab closes, unless you choose to stay signed in across tabs. An admin-level token is held in memory for the one action that needs it, then discarded.
No analytics in the apps
None of our apps runs analytics. This site measures visits only after you consent.
Delivered by Vercel
The apps’ code is delivered by Vercel, which logs each request’s IP address and path. We have not yet confirmed how long Vercel keeps those logs.
What it runs on
We run no database of customer data. These are the services the apps and this site depend on, what each one does, and how far it reaches.
Your Microsoft 365 tenant (SharePoint)
Data storage
Your records live in SharePoint sites and lists in your tenant. The Portal creates one map site that tells each app where its own site is. The lists that hold settings are writable by your admins only, with version history on.
Why: Your data stays under your retention, your backups and your access reviews, and leaving us means switching an app off, not exporting from us.
Microsoft Entra ID (your tenant)
Sign-in
Every web app signs in through your tenant’s Entra ID. The token stays in your browser tab; we hold no password and no user list.
Why: Your admin already runs it, so access is granted and removed in one place.
Microsoft Graph
Reading and writing your tenant
The apps read and write your tenant through Microsoft Graph, from your browser, as the signed-in person.
Why: It is Microsoft’s own interface to Microsoft 365, and it enforces both your admin’s consent and the person’s own permissions.
Vercel
Hosting and delivery
Serves the code of this site and the apps from its network, and runs a short list of server requests: the tools menu, bug reports, health checks, the Portal’s billing check, this site’s contact form and Bid’s scheduled jobs over public federal data. It stores Bid’s public feed, checks forms for bots, and measures visits to this site after you consent. It logs each request’s IP address and path; how long it keeps those logs is not yet confirmed. Your tenant’s data does not pass through it, apart from what you type into a bug report.
Why: One platform builds, deploys and serves every site and app, so a change that passes our checks is live in minutes.
Stripe
Billing
Takes payment and keeps the billing record, including which apps you buy, as our payment processor. Our code only reads a checkout and its subscription; it never writes to Stripe.
Why: Billing is the one record the sale needs, and Stripe keeps it so that we do not.
GitHub
Code, checks and bug reports
Holds our source code, runs every check before a change merges, publishes our shared packages, and receives the bug reports you choose to send, as issues in an internal repository.
Why: Every change, check and report is recorded in one place.
Microsoft 365 (our tenant)
Our own mail
Sends this site’s contact-form mail and holds inquiries in our shared inbox. The site gets a short-lived token for one mailbox and keeps no password.
Why: We run on the same Microsoft platform we build for.
SAM.gov (U.S. General Services Administration)
Public contract data
Bid reads public federal notices from it. Nothing about you is sent to it.
Why: It is the government’s own source for federal notices.
GoDaddy (DNS)
Domain names
Answers which server each of our addresses points to. It sees no app traffic.
Why: It is where the domain is registered.
What it is built with
The main frameworks, not every package
Next.js and React
Every site and web app is a Next.js application, written in TypeScript with React. Most of each page runs in your browser.
Microsoft Authentication Library (MSAL.js)
Microsoft’s own sign-in library for browsers handles every sign-in and keeps the token in your browser.
Tailwind CSS
Styles every page. It runs when we build, not in your browser.
Tauri and Rust
The Windows desktop app, Telemetry, is a Tauri application: Rust reads Windows, and a React screen shows it.
Upcoming: GCC High and DoD tenants
Upcoming: GCC High and DoD tenants. The apps already know the U.S. government cloud’s sign-in and Microsoft Graph addresses. The app registrations in that cloud do not exist yet, so a GCC High or DoD tenant cannot use the apps today.
When they do, we plan to serve those editions from Azure Government instead of Vercel. Azure Government holds a FedRAMP High authorization; Vercel is not listed in FedRAMP’s published Marketplace data (last updated May 19, 2026).
DFARS 252.204-7012 requires a cloud provider that stores, processes or transmits covered defense information for a contractor to meet the FedRAMP Moderate baseline. The apps keep that information in your tenant, and moving their delivery into Azure Government puts the code they run in an authorized cloud too. The apps support your CMMC work; they do not certify you.
Check us yourself
You do not have to take this page’s word for any of it. A technology-detection browser extension, such as Wappalyzer, lists the frameworks, hosts and analytics a website loads. Run one on this site, on our apps, and on every other vendor you are weighing. If you would rather not install an extension, your browser’s developer tools show the same thing on the Network tab.
What a browser recorded on October 26, 2026: before you accept statistics, this site loads nothing from any address but its own. After you accept, it adds one script, Vercel Web Analytics, also from its own address. Our apps load no analytics at all.
Signing in to an app takes you to Microsoft’s sign-in page. That page is Microsoft’s, not ours, and it sends Microsoft’s own telemetry to browser.events.data.microsoft.com. We do not control it, and you will see it on any app that signs in with Microsoft.
On any vendor’s site, count the analytics and tracking tools a page loads. Each one is another company that sees your visit.
Our mission
We build small Microsoft-native apps that do day-to-day IT and compliance work inside your own Microsoft tenant, so you never hand us your data.
Your tenant admin decides who signs in and what each app may do. What we hold about you is billing, nothing beyond what Stripe, our payment processor, holds.
We start with federal agencies and the contractors that serve them, because the cost of their overhead is paid by the taxpayer.
Our vision
Any organization that runs on Microsoft can do its everyday IT and compliance work with tools it controls, without copying its data into a vendor’s systems. We start with the work most organizations do every day and add the rest over time.
Who we build for
We build for the security, compliance and IT teams of commercial companies, federal contractors and federal agencies.
Each app does one job, does enough of it for the day-to-day work, and says what it does not do. The apps share one sign-in and one tools menu, and the set grows from there.
Our apps support your compliance work. They certify no one: the outcome is yours and your assessor’s.
What we hold ourselves to
The public comes first
Every customer is part of the public. We do not build a tool that serves one customer at the cost of everyone else, and when the needs of the many and the needs of one conflict, the many come first.
The risk stays with you
You take on a risk with every vendor. We design each app so that the risk returns to your tenant, your admin and your own controls, instead of resting with us.
Hold only what the sale needs
What we keep about you is billing, because the sale needs it. If a design would need us to store more about you, we change the design.
Your admin decides
Your tenant admin switches each app on, decides who may use it, and removes that access in one place, Entra ID.
Do enough, and say what it does not do
Each app does the everyday part of one job. We state its limits, so you can judge it before you rely on it.
Switch on your first app
Sign in at the Portal with your Microsoft admin account and switch on the first app. There is no call to book.