Your data stays on your servers
Here's exactly what reaches ours
Netlang integrations run on Gateways in your own network. The Netlang cloud manages them and stores only the data described on this page.
How data moves
Integrations run in your network. The cloud is the control plane.
The Gateway runs on your own servers: Windows, Linux, IBM i or Docker. If the connection to the Netlang cloud drops, your integrations keep running. Deploying changes needs the connection.
Data inventory
What stays, what's optional, what reaches the cloud
Stays in your network
- Business data processed by your integrations
- Gateway system logs, written to the Gateway's disk only
- All DEBUG-level logs
- OpenTelemetry traces and metrics, sent to your own monitoring tool
Only if you enable it
- Request and response payload logging (off by default)
- Gateway metrics (off by default)
- EDI document tracking (if used)
- Traffic between Gateways: relayed in transit, not stored
Reaches the cloud
- Integration code and configuration
- Credentials and secrets, stored encrypted
- Integration logs above DEBUG, kept for 30 days. Your code decides what is logged, and cloud logging can be switched off.
Deployment and jurisdiction
Choose how much of Netlang runs on your infrastructure
Standard
Netlang cloud
- Control plane hosted in the EU
- Integrations run on Netlang Gateways in your network
- Gateways connect with outbound TLS
- Software updates downloaded from Netlang
Full control
Self-hosted Master
- Control plane runs on your own server
- Integrations run on Netlang Gateways in your network
- No connection to the Netlang cloud needed
- Updates delivered as installation packages; works fully offline
Jurisdiction
Netlang AB is a Swedish company, founded in 2009. The Netlang cloud is hosted in the EU, and backups stay in the same region. If your requirements call for no external cloud at all, a self-hosted Master keeps the control plane and all Gateways on your own infrastructure.
Security practices
How we protect the platform
Outbound connections only
The Gateway opens an encrypted TLS connection to the Netlang cloud. You don't open any inbound firewall ports.
Encrypted secrets
Credentials and secrets are stored encrypted. Netlang manages the encryption keys itself, and secrets reach the Gateway over TLS when needed.
Multi-factor authentication
The web admin supports MFA for every user account.
External vulnerability scans
We run regular external vulnerability scans of our cloud services and act on the findings.
Incident notification
We notify affected customers within 72 hours of discovering an incident.
Your data and AI
Netlang does not use customer data to train AI models and does not send it to AI services. Your data only reaches an AI service if your own integration is built to call one.
Leaving Netlang
Export your integration code and configuration as Maven artifacts or Eclipse projects. When a contract ends, your data in the Netlang cloud is deleted within 30 days.
Supplier assessments
Supply-chain requirements such as NIS2 mean more customers assess their suppliers. We answer security questionnaires and vendor assessments, and share our information security documentation on request.
Security questionnaire or vendor assessment?
Send it to us. You'll get answers from the people who build the platform. Viktor Claesson, Tech lead.