The public catalog and your internal parts on one instance inside your network. Your tools read it. The internet cannot reach it.
One approved parts list across programs, beside the public catalog your engineers already search.
Isolated networks, procurement rules, and data that is not allowed to leave the building.
Controlled technical data inside an environment and access model you already govern.
The same product your engineers use on satbase.com, with your parts, approvals and files beside the public records. One search, one set of filters, one comparison, across both.
Internal parts and public records on the same template, with your program approvals in the row.
Approvals, qualification files and notes on the record, not in a spreadsheet three folders away.
Filter and compare on the same parameters across both.
Sign-in through SSO. Roles you assign, with an audit log of changes.
The same API the public platform exposes, with keys your administrators issue and revoke. Updates arrive as signed snapshots you can inspect.
SatBase publishes the public catalog as a signed snapshot. On the schedule you set, your instance opens one connection to satbase.com, fetches the snapshot, checks the signature and applies it. Or it arrives on a disk. Either way, the request carries nothing about your users, your parts or your searches.
Nothing about the application changes between them. What changes is where it lives, and how the catalog snapshot gets to it.
The pieces, and what each one asks of your environment. Versions and sizing are in the security overview.
Architecture, data flows, the update mechanism and operational responsibilities. Ask for it in the form below.
Request the documentSix facts about the deployment, each one a design decision rather than a setting.
SAML or OIDC. No local passwords required.
Who changed what, and when, on every internal record.
TLS terminates on infrastructure you control.
The instance reports nothing back. Snapshot requests carry no account, usage or search data.
Verified on the instance before anything is applied.
Your data lives in your database and storage. Stop the licence and the instance keeps running.
Connected deployments are the quickest. Air-gapped installs add the time your own transfer process needs.
We walk through your environment, data sensitivity, identity setup and network constraints with your security and IT teams.
SatBase is installed on hosts you operate. You hold the keys, the certificates and the database.
Import parts lists, supplier records, datasheets and program notes. Turn on public catalog updates, or leave them off.
Your team runs it day to day. We supply releases and support on the cadence you set.
Something else? Ask us directly.
Tell us about your program and environment. We will come back with the deployment shape that fits and what it takes to get there.
What happens next
Prefer a document first? Say so in your message and we will send the security overview for your reviewers.