Deployment
A quick overview of how Datawisp can be deployed.
Deployment Overview
There are several ways to deploy Datawisp based on your needs.
Shared Deployment - app.datawisp.io
Included in pro plan
The pro plan includes access to the shared deployment of datawisp. All of Datawisp’s extensive protections for your data apply. For example, data is encrypted at rest, connections are isolated, and strict access controls are enforced.
Advantages:
Zero Setup
Instant Support
Managed Deployment
Included in pro plan for subscribers with 10+ seats
In the cloud of your choice, Datawisp will deploy a separate instance of Datawisp, only accessible to your users. Datawisp will manage the instance for you. Data is encrypted, and tenants are strictly isolated from each other. The deployment will be in the region of your choice, which also can improve loading times.
Sign-in and account creation will be limited to domains and login methods of your choice.
Advantages:
Zero Setup
Instant Support
Deployment in the region and cloud of your choice.
Data does not leave your cloud provider’s infrastructure.
Supported Clouds:
Datawisp Enterprise Server (Self-Hosted)
Included in enterprise subscription
Datawisp Enterprise Server is a self-hosted version of the Datawisp platform. Your business can benefit from increased control and avoid issues associated with the public cloud, while you can benefit from all features and workflows of Datawisp.
Datawisp Enterprise Server is suitable for enterprises that are subject to regulatory compliance. It runs on your infrastructure and is governed by access and security controls that you define, such as firewalls, network policies, IAM, monitoring, and VPNs.
If your main compliance requirement is for your company's data to reside in a specific region, you may want to consider the Managed Deployment. With this option, you won't need to schedule downtime for maintenance or upgrades, and your users will have access to the latest features and the full support of Datawisp.
Deployment
Datawisp will provide a pre-configured docker deployment via docker-compose. A postgresql database is required. To provide support for your users, Datawisp will collect sanitized logs.
Sign-in and account creation will be limited to domains and login methods of your choice, to prevent unauthorized access.
LLMs
To provide Wispy, Datawisp Enterprise Server needs access to an external LLM. The endpoint and authentication is configurable. By default, Datawisp uses GPT-4o provided by OpenAI, and supports GPT-4o via Microsoft Azure’s Cognitive Services.
For other LLMs, please contact us. Note: performance can vary.
Option: Very Low Egress
If you have especially stringent requirements (e.g. due to regulatory reasons) , Datawisp can be configured in a low-egress mode. This would stop even sanitized logs being sent to Datawisp. In this case, the support workflow for your users changes.
If you are interested in this option, please ask us for details!
Option: Instant Support
Some issues can be resolved instantly by our team. This requires some limited access for some named members of our team to access your instance. In some cases, this reduces friction when resolving issues.
Last updated