Kelynto Managed on Azure, or inside your own account.
Kelynto is one codebase with two ways to run it. This page says what runs where, what crosses the boundary in each model, and how each part is verified. Azure first.
Two deployment models.
The same container images in both. The difference is whose cloud account they run in, and who operates them.
Run by Kelynto
Kelynto Managed
In the Kelynto Managed model your data is stored and processed in Kelynto's Microsoft Azure environment in Central US, separated from other customers in the application and again in the database. Store coordinates are sent to public weather services. A language model receives your weekly facts only when the AI writer is switched on for your workspace.
- How it runs: on Microsoft Azure in Central US, deployed by an automated pipeline with health checks and automatic rollback of the application images.
- How it opens: a workspace is opened with each agreement: a pilot, a partner sandbox, or the workspaces of a partner's clients.
- What you provide: a weekly file or a scheduled export, and the details of your identity provider.
- To start now: a pilot can begin with files exchanged by hand. You send the week's file and we return the drafted review.
Run in your own account
Customer Environment
Kelynto can run inside your own Azure account. In that model your sales, plan and in-stock data, your store list and your users' details are stored and processed in your environment and are not sent to Kelynto. The software does not call home.
- How it is delivered: through an enterprise implementation with your IT team, with the Azure deployment kit that runs Kelynto Managed.
- The first install is done alongside your IT team and verified with the supplied checks.
- What you provide: a resource group, an application registration in your directory, a host name in your DNS zone, and a mailbox for alerts.
- You decide who holds owner access, who receives alerts, and who may open a shell in the containers.
For partners. The workspaces of a partner's clients run on Kelynto Managed, one workspace per client. See the partner platform.
What runs where.
The same components in both models. The database is the only state; everything else is rebuilt from the release.
| Component | Kelynto Managed | Customer Environment |
|---|---|---|
| Web app, API and scheduler | Containers in Kelynto's Azure subscription | The same containers in your Azure subscription |
| Database | Azure Database for PostgreSQL, shared by tenants and separated by row-level security | Azure Database for PostgreSQL in your subscription, one tenant |
| Secrets | Key Vault in Kelynto's subscription | Key Vault in your subscription |
| Sign-in | Your identity provider. A shared provider exists for customers without single sign-on | Your identity provider |
| Logs and alerts | Log Analytics in Kelynto's subscription | Log Analytics in your subscription |
| Backups | The PostgreSQL service's backups, in Kelynto's subscription | The PostgreSQL service's backups, in your subscription |
| AI writer, when it is switched on | The provider chosen for the workspace | Azure OpenAI in your own tenant is supported |
What crosses the boundary.
Your data does not have to leave your environment. By default Kelynto looks up weather alerts and forecasts for your stores by sending their coordinates (no names, no sales) to the United States National Weather Service. You can switch that off, for one workspace or for the whole deployment with a setting no workspace administrator can change. With it off, the built-in writer, and no webhook or scheduled file drop set up by your administrators, the only outbound connection is to your own identity provider, to download its public signing keys.
Optional features send data out only when you switch them on: an event source receives store coordinates, a language model writer receives the week's aggregated facts, including store names and amounts, a webhook sends a summary of a published review to an address your administrator names, and a scheduled file drop connects to the file server or storage your administrator names. A deployment-level setting can forbid each of them for every workspace.
| Flow | What is sent, and where | Control |
|---|---|---|
| Your weekly files | Weekly totals by store and category, sent to the upload endpoint. In the Customer Environment model they never leave your subscription. In the Managed model they go to Kelynto's service. | Totals only. No transactions, shopper, payment or employee data is needed. |
| Sign-in | The browser goes to your identity provider. The API downloads your provider's public signing keys. Nothing about your data is sent. | Your identity provider enforces multi-factor sign-in and conditional access. |
| Weather | Store coordinates and dates. The United States National Weather Service receives a coordinate pair per store, for alerts and the point forecast, with a contact in a request header that you set to your own in a Customer Environment. Open-Meteo, only if an admin switches it on, receives coordinates rounded to four decimals and a date range. No store names and no sales. | The National Weather Service is on by default. Open-Meteo is off by default, and offers its free service for non-commercial use, so an agreement with it comes first. Each source can be switched off per workspace, and all outbound lookups for the whole deployment. |
| Local events | Store coordinates, a radius and a date range, sent to PredictHQ. | Off unless an admin enables the source and the deployment holds a key for it. Forbidden for every workspace when the deployment-level setting is off. |
| Road work | Nothing is sent. State road-work feeds are downloaded and matched to stores inside the deployment. | Off until an admin lists a feed. Addresses must be public https addresses. |
| AI writer | The week's aggregated facts, including store names and amounts. Never raw rows or user details. | Switched on per workspace: by the workspace's admin, or for a partner's clients under the partner's recorded agreement with them. A deployment-level setting can forbid it for every workspace. |
| In-app assistant, model mode | For a question the fixed rules did not recognise, and only then: the question and the name of the page it was asked from. No record and no figure. The model's reply only picks the kind of question and is never shown. | Off by default, at the deployment and in each workspace. The same deployment-level setting that forbids the AI writer forbids it. |
| Webhooks | A small signed message per event to an https address a workspace admin adds: for a published review, the week's figures, the recorded causes with their estimates, the titles of the records on file and the amount not explained. No rows of data, no user details. | Off in a Customer Environment until your operator allows them. Public addresses only. A deployment-level setting forbids them. |
| Scheduled file drops | The credential your admin entered, and requests to list, download and, if chosen, move or delete your files on the SFTP server or storage your admin names. What comes back is your own files. | Off in a Customer Environment until your operator allows them. Public addresses only. A deployment-level setting forbids them. |
| Outgoing mail | Sign-in links, invitations, a review a member sends to approved addresses, reminders and Watch alerts, through the mail relay the deployment names. | Off by default: nothing is sent, and a review or an alert is kept as a draft. |
| Map tiles on Watch | Only if an operator sets a tile address: the browser of the person viewing the map asks it for the tiles of the area shown. No store, record or sales figure. | Off by default. The map draws over outlines the app carries and the browser contacts nothing outside the deployment. |
| The browser | The web app loads its fonts and scripts from its own origin and calls no third-party origin except the identity provider chosen at sign-in. | Enforced by the app's Content Security Policy. |
| Telemetry | None. The software does not call home: no usage telemetry, no licence check, no update check and no error-reporting service. | Checked by reading the code. |
| Deployment-level settings | Nothing is sent. Two settings on the deployment forbid every outbound signal lookup and every call to an external language model, for every workspace. Two more forbid webhooks and scheduled file drops, which ship switched off in a Customer Environment. The settings screen shows them as locked and the onboarding check reports them. | Set by whoever runs the deployment. A workspace administrator cannot change them. Exercised by automated tests. |
| Kelynto staff | In the Customer Environment model, whether Kelynto staff have any access to your subscription is agreed in the contract. | You hold the subscription. |
In both models: Kelynto does not need or store shopper, payment or employee data. It works on weekly sales and plan by store and category. The engine computes every number. The weekly commentary is written by Kelynto's built-in writer, or by Claude when the AI writer is switched on for the workspace.
Azure first.
Azure is the design target: complete, documented templates, the same ones that run Kelynto Managed.
- Azure Container Apps for the web app, the API and the scheduler. The API has internal ingress only.
- Azure Database for PostgreSQL with no public endpoint, in a delegated subnet.
- Key Vault for secrets, read through managed identities. No secrets in code, parameters or images.
- Log Analytics for container, database and Key Vault logs, with email alerts.
- Optional Front Door with a web application firewall in front.
Other paths.
The same images, on other hosts.
- A single virtual machine with Docker Compose. The same images, for a small install, rehearsed end to end in production mode.
- AWS. Available through enterprise implementation. A Terraform module for AWS (ECS on Fargate, RDS for PostgreSQL) is written, and the first install in your AWS account is run with your platform team as its validation run.
- Your own data center. A container path for any Docker host with PostgreSQL, run as an implementation project.
Sign-in, roles and tenant isolation are in the Trust center.
How each part is verified.
What is verified by running it, and what is set up and checked with you during a pilot or an implementation.
| Part | Verified by running it | Set up with you |
|---|---|---|
| Container stack | Run in production mode: database bootstrap, migrations, a smoke test, a full customer onboarding, isolation checks through the API and at the database, and container lock-down. | The pipeline builds the release images and runs them on Kelynto Managed. Your install runs the same images. |
| Azure templates | They compile and lint cleanly, and they run Kelynto Managed. On every merged change the pipeline builds the images, migrates the database, rolls out, runs the health checks and returns to the previous application images if a check fails. | Your subscription, with the private shape of the kit, Front Door and point-in-time restore where you choose them, and a sign-in for each role and a test alert. |
| Sign-in | Exercised end to end against a test identity provider, including tokens that must be refused. | Your Entra ID, Okta or Auth0 tenant, checked with a test sign-in before single sign-on is switched on. |
| Backup and restore | A restore drill of the single-VM procedure. | Point-in-time restore in your subscription, with recovery targets set for your deployment. |
| Outside signals and AI providers | Covered by automated tests with the outside services simulated. The AI writer runs with Claude, by Anthropic, on Kelynto Managed. | The signal sources and the AI provider you choose, switched on per workspace. |
| Scheduled file drops, webhooks, single sign-on set-up and SCIM | Covered by automated tests against stand-in servers and providers. | Your storage service, SFTP server, webhook receiver and identity provider, connected and checked with your admin. |
| Access by store and governed delivery | Covered by automated tests on PostgreSQL 16 as the application's own database role, with two workspaces and members limited to different regions, and by browser checks of the screens. | Your own export and control totals, and store limits set by your identity provider's groups. |
| Scale | Ingest, the weekly run and read latency measured at 500 and 2,000 stores, and a partner's 200 client workspaces, on synthetic data. | A sizing check on your own data volume. |
What your IT team would do.
For a Customer Environment install. This is the planning outline.
- Review Read the Trust center and the security overview. Ask for the review pack.
- Register the application In your identity provider, with the roles viewer, planner, analyst and admin. This step usually sets the pace, because it follows your own change process.
- Deploy Run the templates in a resource group you own, with us alongside, or have us run them with access you grant.
- Verify Run the supplied checks: health, sign-in, security headers, and that a database connection bound to no tenant sees no rows.
- Load and run Stores first, then sales. The first week is run by hand and read together.
Deploy in your environment
- Tell us your cloud, your identity provider and your review process
- We answer in writing, from the code and the documents
- The first install in your account is run alongside your team as its validation run