PUBLISHED DATE: 2026-09-29 04:01:31
AI modernization built for enterprise security
Secure SaaS deployment guide
Slingshot’s dedicated SaaS deployment is built for enterprise organizations that need strong security, strict data isolation and clear governance without the time and operational complexity of running the platform in their own cloud environment.
Hosted in your preferred cloud provider and region, this deployment model provides dedicated infrastructure, controlled data handling and clear data residency guarantees, enabling the secure ingestion of proprietary source code and related artifacts.
In a dedicated SaaS deployment, Slingshot runs in a single-tenant, isolated environment hosted by Publicis Sapient in client-approved cloud regions.
This means:
- Your infrastructure is not shared with any other client
- Compute, storage and databases are dedicated to your environment
- All customer and backup data remains within the selected region
- Processing workloads execute in the same region where the data resides
- You benefit from a fully managed SaaS experience while maintaining strong isolation comparable to a client-hosted installation
A dedicated environment designed around your needs
Supported cloud environments include:
How Slingshot handles and protects your source code
Slingshot is built to ingest and process client source code in a controlled, time-bound manner:
- Raw source code pulled from client repositories is held only in temporary processing buffers
- Source code is deleted immediately after vectorization
- Only vector embeddings (numerical representations of code logic) are retained
- Embeddings are isolated per client
- Client code is never used to train Publicis Sapient models or third-party LLMs
This approach minimizes the persistence of raw intellectual property while still enabling AI-assisted modernization workflows.
Why choose dedicated SaaS vs. client-hosted?
For many organizations, dedicated SaaS offers the right balance between control and simplicity.
Instead of standing up and maintaining infrastructure in your own cloud, you can rely on a managed environment with clearly defined security, residency and retention controls.
Dedicated SaaS provides a security posture comparable to a client-hosted deployment while delivering faster time-to-value and lower operational burden.
Clear controls for data residency and retention
Slingshot enforces clear data residency and retention policies. All customer data is stored only in the chosen deployment region and clients can request data deletion on demand in addition to standard off-boarding cleanup.
Default retention periods vary by data type:
- Transient execution data: removed immediately after use
- Source code: deleted immediately after vectorization
- User conversations: retained for up to 3 months (deletable on request)
- Analytics data: retained for up to 6 months
- Prompts, embeddings and configuration data: deleted during off-boarding
- Backups: retained for up to 1 month then automatically deleted
Security controls built into the platform
Robust security controls are embedded across the platform:
- Encryption at rest and in transit for all customer and application data
- Role-based access controls (RBAC) to restrict access to authorized users
- Centralized logging for access events, authorization activity and security-relevant actions
- Logs are retained in the deployment region and rotated according to policy
Responsible and controlled use of generative AI
Slingshot uses enterprise LLM agreements within each dedicated client environment.
- Client data is not used for model training or fine-tuning
- AI-generated output is subject to human-in-the-loop validation
- Quality checks are applied before outputs are incorporated into delivery workflows
This ensures AI assistance is applied responsibly, transparently and with appropriate safeguards.
Deliver new software and modernize legacy systems with confidence.