Integrations
Fits the stack you already run.
Your databases, your identity provider, your choice of AI model, your repositories and your deployment target. Connected once under Integrations and reused by every application. One honest sentence on each, no logos.
Databases and data
Connect to your data where it lives. Connected tables sit beside the internal ones and feed screens, functions and charts.
MySQL
Point PIES Studio at an existing schema, or let it generate the internal database from your model with no DDL.
PostgreSQL
The same modelling, preview and export path as MySQL.
Snowflake
Connect a warehouse and use its tables in screens, functions and charts like any other source.
Zetaris
Read-only analytics over a token-based REST connection to the Zetaris data platform. The retail banking templates are built on it.
Views and formula columns
Read-only views with joins and typed formula columns over internal and connected tables.
Learn more →Fail-loud by design
An external source with no credential never falls back to a local copy, and a deploy with a missing database secret is blocked.
Learn more →AI models
Use the model that suits each task. Policies, not developers, decide which model may see which data.
Anthropic Claude
Connect with your own API key. Optional, and subject to Anthropic policies for any data you allow it to see.
OpenAI
Connect with your own API key. Optional, and subject to OpenAI policies for any data you allow it to see.
Azure OpenAI
OpenAI models inside your own Azure subscription, routed and governed like every other model.
xAI Grok
Connect with your own API key, routed and governed like every other model.
PIES LLM
Private models included with Enterprise, run on your own hardware. No external calls, works air-gapped.
Learn more →Policy routing and audit
Redaction before any cloud model, per-call audit with user, model, classification and tokens. Key health shown in AI Settings.
Learn more →Agents and APIs
Every application is a building block that people, systems and AI agents can call.
REST API with Swagger
Every running app serves /docs, /swagger and /openapi.json for its own API, in Go, Python or Java.
MCP server per app
A Model Context Protocol server with a tool per table and a tool per function, used by the app's agents and the in-app chatbot.
API Connections
Define an outbound REST call once, press Test, and use it from a REST Call step in any function.
Webhooks
Trigger an agent from any system that can post to a signed webhook.
Learn more →In-app AI agents
Agents that work inside the app as an access group, with approvals where you want them.
Learn more →Platform APIs
Agent and playbook endpoints are stable across releases, so you can script them.
Identity and access
Sign in with the directory you already run, in the Studio and in every application you build.
Studio: Microsoft SSO
Single sign-on to PIES Studio with Microsoft on Enterprise.
Generated apps: SAML and OIDC
Every application signs its users in with SAML, OpenID Connect, Microsoft, Google, Apple, PIES Studio or a password, configured once.
Learn more →Secrets in Vault
HashiCorp Vault holds API keys, database passwords and tokens, referenced by name.
Learn more →Code export and source control
Standard source code in the languages your engineers already know. Yours to keep.
React / Next.js
Front ends exported as standard React projects.
Angular
Front ends exported as standard Angular projects.
Go
Back ends exported as Go services with typed routes.
Python
Back ends exported as Python services.
Java
Back ends exported as Java services.
Flutter
Mobile apps generated from the same definition, with the source and a debug APK to download.
GitHub
Push generated code straight to a GitHub repository.
Bitbucket
Push generated code straight to a Bitbucket repository.
Mobile publishing
Connect your store accounts once and every application can use them.
Apple
Connect an Apple developer account for publishing the Flutter app under your own name.
Google Play
Connect a Google Play account the same way.
Deployment
Run it wherever your infrastructure lives. PIES does not host your data.
Docker
Previews, builds and deployments run in real Docker containers. Docker Engine 24+ with Compose v2 on Linux.
Kubernetes
Deploy to a Kubernetes 1.26+ cluster you connect under Integrations.
AWS
Connect AWS credentials once and deploy any application into your own account.
Azure
Connect Azure credentials once and deploy any application into your own subscription.
On-premises and air-gapped
Fully functional with no internet connectivity when paired with PIES LLM.
Install guide
Requirements, ports and the installer for the Enterprise trial.
Learn more →Collaboration
Where your team already talks.
Microsoft Teams
A Teams connector set up under Admin.
Your SMTP server per environment, for branded platform email and the Send Email step in your applications.
Cloud model providers are optional. PIES Studio is fully functional with PIES LLM alone, and data sovereignty guarantees apply when you use PIES private models. Something missing? Ask us.
Connect it to your data this week.
Install the 60-day Enterprise trial on your own server and point it at your database.