Security
How Parikalp handles your engineering data
Design data is the most sensitive thing a hardware company owns. Here's where it lives, who can see it, and what we never do with it.
Security principles
- You choose where it runs
- Team plans run on our cloud-hosted models. Enterprise customers can run Parikalp entirely on local models inside their own infrastructure.
- Your files stay where they are
- Parikalp reads from your existing drives, CAD vaults and PLM exports. Nothing is migrated, and your systems of record stay the source of truth.
- Never used to train shared models
- Your CAD files, simulation results and design notes stay in your deployment. They're never shown to other customers or used for training.
- Encrypted in transit and at rest
- Every file and every question is encrypted. On on-premise deployments, nothing crosses your network boundary at all.
- Access by role, with an audit trail
- Decide who can ask about which projects, and see a log of every search, so sensitive programs stay with the people cleared for them.
- Answers you can check
- Every answer links to the files it came from, so engineers verify the source before they act on it.
Deployment options
| Cloud (team plans) | Your infrastructure (enterprise) | |
|---|---|---|
| Where the models run | Parikalp's cloud-hosted models | Local models inside your own infrastructure |
| Where your files stay | On your existing drives and systems | On your existing drives and systems |
| Network boundary | Encrypted in transit and at rest | Nothing crosses your network boundary |
| Training on your data | Never | Never |
| Access control and audit log | Yes | Yes |
Export-controlled and sensitive programs
For programs where technical data must not leave your network, such as export-controlled defense work, run Parikalp on-premises on local models. Combined with project-level access rules and the search log, sensitive programs stay inside your infrastructure and with the people cleared for them.
During the closed beta
Teams in the closed beta sign an agreement with us that covers how their engineering data is handled. Before any files are connected, we walk your engineering and IT leads through the deployment options and data flows, and we start with the projects you choose.
This page covers the product. For the information you share through this website, such as the early-access form, see our privacy policy.
Questions from your security team
Send them to parikalp.me@gmail.com and we'll answer them directly, or raise them on your first call.
Related
Bring your security questions to the first call.
We're onboarding engineering teams of 20 to 500 people for the closed beta. We'll map where your data lives and which deployment fits before anything is connected.