v26.04-2 Release Note
Update to Parashift API & Domains.
We are migrating our infrastructure [1] and have also taken the opportunity to clean up the subdomains used by the Parashift app.
This means that some subdomains you use with Parashift will change a little.
Your tenant(s) are currently hosted at our Swiss hosting provider [2]. This will remain unchanged.
Action needed
You will need to update the endpoint URL used by your integration.
Please confirm when you have updated your firewall rules (allow list), or let us know if this doesn’t apply to your setup.
If you use webhooks, note that we now provide a single static IP per region.
For example, accessing the app at https://app.parashift.io will stay the same, but integrating with https://api.parashift.io will change to https://api-ch.parashift.io.
The new set of subdomains will be [3]:
- app.parashift.io - the frontend application
- id.parashift.io - login, user/tenant management
- assets.parashift.io - user avatars, tenant logos
- api-ch.parashift.io - the backend and api (where your data is processed)
- storage-ch.parashift.io - the backend file storage (where your data is stored)
- webhooks-ch.parashift.io - webhooks management, with a static IP [3]
- errors-ch.parashift.io - error reporting used for support
- llm-service-ch.parashift.io - llm configuration, chat with document
And we will stop (or already have stopped) the use of:
- id.api.parashift.io
- individual-extraction.api.parashift.io
- webhooks.api.parashift.io
- storage.parashift.io
- storage.googleapis.com
- fonts.googleapis.com
- fonts.gstatic.com
- *.sentry.io
What this means for you?
API
For access to the API, your technical administrator/developer switches the endpoint URL
- from: api.parashift.io
- to: api-ch.parashift.io
We will serve on both endpints for a limited time, so you can do this when it suits you best.
App
If your security team has NOT implemented firewall rules to restrict the domains (websites) that can be accessed by your users, let us know via support@parashift.io.
If you ARE using firewall rules, first add the new domains and let us know via support@parashift.io.
We'll then flip a switch, and the new domains will go into effect for your users. You can then proceed to remove the discontinued domains. Here too we run in compatibility mode for some time, so you can schedule this according to your IT processes.
Webhooks
If you DO NOT use webhooks, or have NOT limited incoming traffic by IP, there is nothing to do.
If you DO have webhooks enabled, and have limited incoming traffic to an IP range, you can narrow this to one static IP, see [3]. The static IP is within the current range, so you're free to do this whenver suits your organisation best.
We do urge all tenants to make these changes as soon as possible, as they also represent tighter security policies on your end. There is also a slight performance penalty associated with fetching files under the compatibility mode.
In 6 months (October 2026), we will completely discontinue the use of the old domains for all tenants.
If you have any questions or want support during the transition, feel free to reach out to support@parashift.io
Additional Information
- There are two drivers for the infrastructure change: Infrastructure as Code (IaC), and multi-region. With IaC we take a significant step in improving our infrastructure management layer, assuring consistent, secure, and scalable infra with reduced maintenance effort, and pave the way for multi-region and multi-cloud.
With our multi-region initiative, we enable clients to choose their data-residency and processing geography. We already welcome new customers in the DE region, and existing customers will remain in the CH region, but on IaC-provisioned infrastructure. - DE tenants are of course hosted in the German complicance zone. For those, substitute "-de" where it says "-ch" in the mentioned subdomains.
- The static IPs for webhooks are:
webhooks-ch: 34.65.65.151
webhooks-de: 34.89.133.19