Calisto Pro
Calisto Purview

Build your operations on a platform that you will never outgrow.

Calisto Pro supports your business today and tomorrow with tools that will scale your business. Everything your team creates is saved in Purview, not on their computer or personal email. The more you use Calisto Pro, the system documents how your business operates so your operations become consistent and clients know what to expect.

Start NowExplore Features

Multi-Currency · Unlimited Locations · Centralized Governance

Purview · Settings Hub
SettingsGrand Hotel · Santo DomingoLocked onlyExpand all
▾
Core
The catalog every other app reads
7 apps · 38 settings 14 locked
▸
Bookings
6 settings · 3 locked
▸
Inventory
5 settings · 2 locked
▸
Listings
4 settings · 1 locked
▾
Tickets
5 settings · 4 locked
Required fields & QR
What a buyer must give up before a pass is issued
Locked by A. Reyes
Confirmation & reminders
The messages that go out after a sale
Managed by Blueprint
Refund window
How long a holder may return a paid ticket
Lock
▸
Commerce
Sell it, quote it, sign it, get paid
8 apps · 46 settings 19 locked
▸
Ops
Run the floor, the route and the ledger
10 apps · 52 settings 8 locked
▸
Nexus
Every screen a customer ever sees
6 apps · 31 settings 31 locked
▸
Interact
Talk to people on every channel
7 apps · 28 settings 4 locked
Calisto Purview

The Business App for Every Business Unit

Locations, policies, team structure, data residency, and server-side enforcement. The operating identity every other app reads.

What You Control

Everything set from one place, for every business unit at once.

Learn more →

The Model

Pick the concept your business runs on and the screens follow it.

Learn more →

Built to Grow

What changes when you add a second location, or a fiftieth.

Learn more →

Enforcement

Server-side, so a rule holds whichever app does the asking.

Learn more →

Policies

What a policy actually is, and what happens when one is broken.

Learn more →

Your Data

Where it lives, who can reach it, and what leaves.

Learn more →

Team

Who belongs to which unit, and what that gives them.

Learn more →

Your Work

Where everything your team creates ends up, and stays.

Learn more →
Why platforms fail you

You did not outgrow your ambition. You outgrew your software.

Three things happen in this order to almost every business that succeeds, and the third one is the only part anybody sells you.

Your software works until you grow

You built your business in one place. It worked. You were ready to expand and your software was not. You needed a second account because it could not handle a second currency. Your providers would not sell you the same tools in a different country. The reward for growing your business was rebuilding your operation from scratch.

✓Your tools forced you into separate accounts per country
✓Your integrations did not cross borders
✓Every new location meant new contracts, new training, new logins

Integrations connect your tools. They do not run your business

The answer the industry gives you is integrations. Connect this to that, sync this with the other thing. But an integration can move data between apps. It cannot enforce a rule across them. Your cancellation policy lives in your booking tool, your refund logic lives in your payment tool, your confirmation message lives in your email tool. Change one policy and you change it in three places, then hope you did not miss one.

✓Every integration is a seam where data gets lost or contradicted
✓When one provider changes their API, your whole stack breaks
✓You become the integration layer, and your time is the glue

One platform. One account. Every location

Purview is one account for your entire business, everywhere it operates. One location or fifty. One currency or twelve. When you open a new location you are not starting over, you are extending what already works: the policies, the brand, the templates, the pricing structure. Adjust what is different and go.

✓No integrations to maintain, because every app reads the same data
✓No software to replace when you cross a border
✓No rules to re-enter, because a policy written once holds everywhere

You should not be the integration layer for your own business. And you should not have to replace your entire stack every time that business evolves. The restaurant that starts catering. The salon that starts selling products. The rental manager who adds experiences. Every one of those pivots means new software everywhere else. Not here.

What you control from one place

Everything that defines how your business operates.

Not settings scattered across the apps that happen to use them. The policy is a fact about your business, so it is stored on your business and read by whichever app runs the operation.

Your business identity

Legal name, tax ID, domain, operating hours, currency. Set per location, managed from one place, and printed by every app that issues a document in your name.

Your booking and scheduling rules

How far ahead, how late, turnaround buffers, overbooking policy, waitlist rules. Written once, enforced in every app that takes a booking.

Your cancellation and refund terms

Free-cancellation windows, penalty tiers, no-show charges, deposit terms, as reusable policy templates rather than settings buried inside each app.

Your pricing structure

Rate tiers, inclusion levels, commission splits. The structure lives here and the pricing app fills in the amounts, per location and per currency.

Your team access

Who is in, what they can see, and what happens when they leave. Access is binary, so there is no role hierarchy to maintain.

Your brand

Logo, colours, voice, preferred terms, blocked words. Defined once, read by every surface your business publishes.

Your distribution channels

Which channels each location sells on, what content each channel gets, and the per-channel overrides.

Your data

Encrypted, EU-based and backed up. Or connect your own PostgreSQL and object storage.

0

screens that control your entire operation

0

operations that act on a whole business unit

0

integrations required

0

additional cost

One system

When you change a policy in Purview, every app already knows.

Not because it synced. Not because a webhook fired. Because every app reads from the same place. Nothing to break, nothing to reconcile, nothing to maintain.

Built to grow with you

From one location to fifty. Nothing changes.

Six screens, in the order you will meet them. Each one is a day in an expansion rather than a category of setting.

Open a second location

Create a business unit that inherits your existing policies, brand and templates. Adjust what is different, currency, hours, tax ID, and go.

Settings · eight suites
Core7 apps4 locked
Commerce8 apps8 locked
Ops10 apps3 locked
Nexus6 apps5 locked
Interact · Work · Engage · Create23 apps

Set company-wide standards

Lock any setting from headquarters and push it to every location. A locked field cannot be changed locally: the write is rejected, not just hidden.

Config Rules
CurrencyDOP
TimezoneAmerica/Santo_Domingo
Operating hours08:00 – 20:00
Legal nameRegistered
Edit from any apprejected server-side

Control who sees what

Restrict a team member to specific locations, specific apps, or specific fields, without building a role hierarchy. One named rule, applied to a person.

Data Rules
Front desk12 membersrole
Santo Domingo only2 locationsteam
Auditor1 personperson
Bound to the roleevery member inherits

Keep every location consistent

Push templates, canvases and brand standards to every business unit at once. Downstream locations can use them and cannot change them.

Standards Hub
148
Canvases
96
Blocks
34
Collections
Checkout canvasBlueprintfrozen
Receipt blockBlueprintfrozen
Storefront heroBlueprintreleased

See where your content came from

One dashboard shows how much of your estate is locked, how much came down from headquarters, how much was purchased, and how much your own team made.

Governance posture
Locked62%
From Blueprint41%
Shared with you18%
Purchased9%
Your own team32%

Onboard a new hire in one action

Apply a saved policy set, which apps they see, which notifications they get, which capabilities they have, instead of configuring every field.

Policy sets
Floor staff14 applied
Shift manager6 applied
Contractor3 applied
Hours
Notifs
Apps
Caps
New teammateone pass, not field by field
Settings · eight suites
Core7 apps4 locked
Commerce8 apps8 locked
Ops10 apps3 locked
Nexus6 apps5 locked
Interact · Work · Engage · Create23 apps
Server-side enforcement

A lock is not a hidden field. It is a refused write.

Most software makes a setting read-only by hiding the button, and the value can still be changed by anything that does not go through that screen. Here the rule lives with the data, so it is the server that says no. Three mechanics, three screens: each one holds whichever app the change came from, and whether it came from an interface, the API or an automation.

When you lock a setting, nobody can change it. Not from any app, not from any screen

This is not a read-only field somebody works around. Lock the cancellation policy and every app that touches cancellations gets the same answer: no. The write is rejected by the server whichever app it came from, whether the change was attempted in an interface, through the API, or by an automation. The lock also records who set it and when, so a standard set at headquarters is visibly not yours to release.

Purview · Config Rules
Config Rules9 fields lockedUnlock allSave
Locked settings cannot be changed in the apps. A write to one is rejected server-side.PATCH → 403
Business Identity2 locked
Legal NameGrand Hotel Caribe SRL Locked by R. Núñez
Domaingrandhotelcaribe.com Locked by R. Núñez
Tax ID1-31-00000-0Lock
Locale and Formats2 locked
CurrencyDOP Managed by Blueprint
Localees-DO Managed by Blueprint
Measurement UnitsMetricLock
Brand2 locked
Brand Colors5 roles set Managed by Blueprint
Logogrand-hotel-mark.svg Managed by Blueprint
What a policy actually is

Six categories. One place. Every app downstream.

Pick a category and you are looking at the screen that governs it, not a description of one.

How far ahead someone may book, how long a turnaround takes, and what happens when you are full. These are facts about how the business runs, not preferences inside a booking tool.

Because they are stored on the business, the same hours bound the schedule in Bookings, print on the directory listing, and answer the question a guest asks the website at 2am.

Purview · Settings · Bookings
Settings · BookingsManaged in PurviewSave
Business HoursFeeds scheduling, directory listings and Google Business
Managed by Blueprint
Monday07:00to23:00Tuesday07:00to23:00Wednesday07:00to23:00Thursday07:00to23:00Friday07:00to01:00Next daySaturday08:00to01:00Next daySunday08:00to22:00
Service periods
4
Breakfast, Lunch, Dinner, Late
Seasons
3
Low, Shoulder, High
Departure templates
11
Per experience, per weekday
Your data · Where it lives

Your database. Your storage. Your choice.

Managed, encrypted and EU-based from day one. Or point at your own whenever you are ready.

Purview · Infrastructure
Database and StorageGrand Hotel Caribe SRLCheck Now
Calisto Box File Storage
Your files, documents, photos, recordings, and attachments.
Healthy
Calisto Box. Stored securely on our servers in Germany. Encrypted at rest.
Connect your own storage provider
Calisto Cloud Database
Every record every app reads and writes.
Your provider
Your own PostgreSQL · db.grandhotelcaribe.com
Connected 4 March · Schema initialised · Last checked 6 minutes ago
Update configurationSwitch back
Infrastructure HealthLast run 6 minutes ago
FilesCalisto BoxFrankfurt, GermanyHealthy
DatabaseYour provider (PostgreSQL 16)Latency: 14msHealthy

Managed needs no configuration

Files in Germany and the database in France, encrypted and backed up. Most businesses never change it, and nothing here has to be set up before you start.

Or point at your own backend

An organization account can use your own PostgreSQL and your own S3-compatible object storage, which is a setting rather than an enterprise contract.

Tested before it is committed

The schema initialises from this screen rather than through a migration project.

A bad credential says so

You get a specific error instead of a silent failure, and you can read a connection's health before switching to it.

Your access is never at risk

The authentication control plane always stays on the managed database, so a mistake in your own infrastructure cannot lock you out of the account.

Team management

From onboarding to offboarding. One flow.

Access is binary and there is no role hierarchy inside an account. Someone is in the business unit or they are not, and what they may change is decided by locks rather than by rank.

Invite
Invite by email, several at a time, or hand out a join code with a use limit and an expiry. Anything still pending can be resent or revoked.
Apply a policy set
A membership policy set covers time, notifications, apps and capabilities. Apply one to a new member and they start configured, rather than being set up field by field.
Scope access
A data rule narrows three things at once: which apps the person sees, which locations they see data from, and which fields are hidden inside those apps. It is a named restriction, not a rank.
Transfer
Membership moves to the new business unit and everything they created stays where it was filed, still attributed to them.
Offboard
One flow severs access and cascades the revocation: membership, sessions pinned to this purview, site grants, space grants, share links they created, pending invitations. Each class is revoked and counted back. Every document, design and customer interaction they made stays with the account.
Your business will change

Start a restaurant. Become a caterer. Add a food truck. Nothing breaks.

Businesses do not only grow bigger, they grow different. The hot dog stand discovers it is really an ice cream company. The hair salon starts selling products. The vacation rental adds tours. Add a business type in a few clicks, with no migration and no new tools.

Start a restaurant

Pick Dine as your concept type. The catalog becomes a menu, the customer becomes a guest, and the screens that lead in every connected app are the ones a kitchen needs.

→

Become a caterer

Add Projects alongside it. Quotes, engagement templates and capacity rules arrive; nothing about the restaurant is removed or migrated to make room for them.

→

Add a food truck

A second business unit inherits the policies, the brand and the templates that already work. Adjust the hours and the tax ID, and it is trading.

→

Nothing breaks

Your data stays. Your team does not retrain. Your policies still hold. On every other platform each of those three steps meant new software, new setup and starting over.

11 business types, one platform

Pick your primary. Add others as you evolve.

Each concept type seeds the catalog structure, the terminology, and which screens lead in every connected app. Start with one, and add another the day your business changes. Nothing is ever removed: every concept screen stays available whatever you pick. A twelfth option, Other, keeps the catalog neutral.

Market
Physical and digital goods with variants, compliance, stock rules, shipping, and gift cards.
Capabilities
Inventory, orders, storefront
Terminology
Customer → Product
What the account keeps

Everything your team makes belongs to the business.

Not to a laptop, a personal login, or the person who happened to make it.

Every document your team ever made, in one place

Documents, spreadsheets, decks, Studio designs, live proposals and the portals your team built, listed across every teammate rather than per person. This is what an account is: the work is filed under the business, not under whoever happened to be holding the laptop.

DocumentsStudio designsProposalsNavigator portals

Attribution that outlives the employee

Creator and last editor on every row, and both keep resolving to a name for people who are no longer on the account. Nothing becomes anonymous the day somebody leaves.

CreatorLast editor

Every screen you have published

Websites, apps, portals, kiosks, terminals and signs. Set the domain, decide who may edit it, take it live, or retire it.

Scoped by account alone

No per-user filter sits between you and the work, so nothing is orphaned when a person leaves and nothing was private to them in the first place.

Opens in the app that made it

Governance is a view over the work rather than a second copy of it. Click a row and you are in Docs, Studio or Proposals, editing the original.

Control at this level is normally something a business grows into: it arrives with a compliance department, an implementation project, and a contract that starts in the tens of thousands. Here it is on from the day you open the account, whether that account has four people in it or four hundred. Your brand, your data, your processes and your institutional knowledge are protected by default, and the 53 screens are there for the day you want more.

Companion apps

What a Purview operator reaches for next.

2 of these 8 connections are in your plan today. The rest stay visible so you know the instrument is there before you need it.

Purview
Blueprint
Catalog
Pulse
Payments
Ledger
Workforce
Ethos
Assure

Blueprint

Blueprint sits above Purview, not beside it: a standard set at headquarters arrives in each business unit already locked and stamped with where it came from.

Learn more →

Catalog

The concept types picked here seed the catalog canvases, templates and business structure that every concept shell renders.

Learn more →

Pulse

The rate structure is defined here and the amounts are not: Pulse fills those in per location and per currency, inheriting the governed structure.

Learn more →

Payments

The currency and tax rate Payments reads are owned here, and a charge is refused rather than guessed when the currency is unresolved.

Learn more →

Ledger

Currency, tax regime, tax categories, commission structures and business identity come from here, while the chart of accounts and the fiscal year stay in Ledger.

Learn more →

Workforce

Crew role, provider and instructor definitions live here, and Workforce reads and writes them in place rather than keeping its own copy.

Learn more →

Ethos

Defining the brand is free and happens here. Ethos is what enforces it, reading this definition on every publish so a locked palette is a check that runs rather than a guideline someone remembers.

Learn more →

Assure

The selected purview scopes every Assure list and metric, and a settings field governed from here renders read-only with the source that manages it named on it.

Learn more →
Pricing

No setup cost. Pay when you start using.

Account setup for every Calisto app.

Included with every Calisto account

Account configuration and data rules.

0Additional Cost
Start Now

Recommended for you

Works well together.

Calisto Blueprint

Included with every Calisto account

HQ rules and governance.

Learn more →
0Additional Cost
Start Now
Calisto Catalog

Calisto Commerce

Catalog, pricing, payments, proposals, contracts, and CRM

Learn more →
2%of revenue processed
Start Now
Calisto Pulse

Calisto Commerce

Dynamic pricing engine.

Learn more →
1%of revenue processed
Start Now
Calisto Payments

Calisto Commerce

Catalog, pricing, payments, proposals, contracts, and CRM

Learn more →
2%of revenue processed
Start Now
Calisto Ledger

Calisto Ops

Full accounting.

Learn more →
€40/user/mo
Start Now
Calisto Workforce

Included with Commerce or Ops

Reservations, inventory, contacts, tickets, and scheduling

Learn more →
0Additional Cost
Start Now
Calisto Ethos

Calisto Engage

Brand guard. Checks brand tone across every app in Calisto Pro — customer service in Desk, designs in Studio, flyers in Docs, presentations in Slides, social posts in Impreta. Enforces brand consistency everywhere.

Learn more →
€25/brand/mo
Start Now
Calisto Assure

Calisto Ops

Daily dashboard, helpdesk, dispatch, accounting, compliance, and HR

Learn more →
1%of revenue processed
Start Now
Spec Sheet

Everything included in Calisto Purview.

Business Units
  • Unlimited business units per account
  • Per-unit location, legal identity, currency, and operating hours
  • Business unit groups for co-located operations, with per-facet sharing rules
  • Brand, catalog, and the rest each shared across a group or not, on its own
  • Independent configuration per unit, centrally governed
  • Each unit provisioned as its own account
  • Terminology: per-unit vocabulary overrides resolved by every screen in every app
  • Per-concept terminology suggestions, offered and never auto-applied
  • Completeness: a derived score per area, on the home grid card and the unit page
Concept Types
  • Market: physical or digital products with stock
  • Dine: menu items composed from inventory via recipes
  • Time-Slots: fixed-price bookable services, instant book
  • Projects: quote-based professional services with proposals and scope
  • Experiences: itinerary-based activities with departures
  • Stays: property and room management with nightly rates
  • Events: date-bound gatherings with ticketing and production
  • Real Estate: properties, developments, and brokerage
  • Rentals: duration-based asset availability
  • Artists: talent profiles, booking, and touring
  • Active: races, endurance, competitions, and fitness
  • Other: neutral defaults when none of the eleven fit
  • Pick one as the primary and add any others that apply
  • A pick seeds prominence and terminology, never a filter
Portfolio Tools
  • Copy: duplicate a business unit, with its configuration and team optional
  • Split: seed a new unit from an existing one, operational data stays behind
  • Split confirmation lists exactly what did not move
  • Share: grant a person or another account view, configure, or govern access
  • A share acceptance code shows once, because only its hash is stored
  • Merge: copy chosen fields into a target unit, move the team, archive the source
  • Archiving a merged source preserves the record and its history
  • Enforce: push one unit's field values onto targets and lock them there
  • Enforced fields read "Managed by Purview" downstream and cannot drift
  • Transfer: move ownership of a canvas between units, body untouched
  • New Purview: the guided setup flow for a unit from scratch
  • Offboard: sever a member and cascade the revocation across six classes of access
Per-App Configuration
  • Eight suite sections in the sidebar: Core, Commerce, Ops, Nexus, Interact, Work, Engage, Create
  • An app grid per suite, plus a settings row for every app in it
  • Settings: every app, governed configuration blocks scoped to this unit
  • Canvases: the screens an app renders, authored and locked here
  • Surfaces: websites, mobile apps, portals, kiosks, terminals, signage, filtered per channel
  • Templates: receipts, designs, sites, kiosks, campaigns, documents, proposals
  • Forms: the locked PDFs and fillable documents Depot and Sign render
  • Catalogs & Systems: which operational systems this unit turns on
  • A deep link from every settings row into the app itself
  • Deals, Mail, and Inbox open onto the shared message-template library
  • Docs, Sheets, and Slides share one document-template domain
  • Depot and Forms open onto the forms library; Sign onto forms and proposals
  • Station, Kiosks, Sites, Apps, Display, and Navigator open onto their surfaces
  • Studio opens onto design templates, Campaigns onto campaign templates
  • WiFi carries the captive portal screen; Direct carries the creator page
Account Work Product
  • Documents: every Docs, Sheets, and Slides file on the account, filtered by editor type
  • Studio designs: every design across every teammate, separate from each person’s My Designs
  • Proposals: every live proposal sent to a client, with status on every row
  • Navigator portals: every portal your team built
  • Published screens: every website, app, portal, kiosk, terminal, and sign
  • Set the domain on a published screen, decide who may edit it, take it live, or retire it
  • Scoped by account alone, so no work is orphaned when someone leaves
  • Creator and last editor shown on every row
  • Creator and last editor resolve to display names for people no longer on the account
  • Each record opens in the app that made it
The Catalog Model
  • Schema-driven catalog structure per concept type
  • Currency set per business unit and read by every app
  • UI language and guest language set per business unit
  • Item model with variants, attributes, and categories
  • Rate structures and pricing rules
  • Defined in Purview, operated in Catalog
The Shared Configuration
  • Business identity: legal name, trading name, domain, tax ID
  • Contact: contact email and contact phone
  • Address: street, city, region, and country, locked as one
  • Business hours: the weekly opening schedule
  • Locale: currency, timezone, and BCP 47 language and region
  • Brand: logo and the primary and secondary brand colors
  • Catalogs: which concept catalogs this unit runs
  • Work: working hours, sending address, and team defaults
  • Every group carries a lock, and a locked value holds in every app
Governance
  • Settings hub: every setting in every app by suite, with a lock on each
  • Suite, app, and setting levels each show how many locks are already set
  • Config rules: locks on the shared configuration, rejected server-side
  • Data rules: named restriction sets bound to a role, a team, or a person
  • A data rule scopes which apps and which locations its target sees
  • Surface rules: how much content is locked and where it came from
  • Standards hub: canvases, blocks, and collections per app, by suite
  • Freeze or release anything Blueprint pushed down
  • Policies: saved membership sets for hours, notifications, apps, capabilities
  • A lock is the only thing that makes a field read-only, everywhere at once
How Enforcement Holds
  • A write to a locked field is rejected by the server with a 403, from any app and any sender
  • The read-only screen is a courtesy; the rejected write is the control
  • Lock provenance: every lock records whether it came from Blueprint or a local admin
  • Headquarters beats local: a lock set above the unit is read-only inside it
  • A lock names its source in the interface, so nobody guesses why a field will not move
  • The headless cascade authenticates with an internal-service secret, with no user session
  • Every cascaded write scopes to the target account, never to the one pushing
  • Tax cascade: company-standard tax configurations upsert per account and per source item
  • Pushing a tax standard again refreshes the rows rather than duplicating them
  • Content sync: canvases, blocks, collections, and templates cascade on the same path
  • Each synced item carries its own auto-update choice
  • Target specificity: a rule bound to a person beats team, which beats role
  • Field-level redaction: a per-app map of fields the target may not see
  • Fail-open: no applicable rule means everything is visible
  • A rules error also means everything is visible, so governance never breaks an app
  • Data rules narrow reads and never block a create
Team & Access
  • Members: everyone with access to this business unit, with role, contact, and reach
  • Owners: a set of people carrying governance and billing authority
  • Add member: the guided hire flow, access and configuration in one pass
  • Invitations: outstanding invites and invite codes with what each grants
  • An invite code opens a public join page; accept, decline, and leave are first-class
  • Spaces: three types, work, personal, and client
  • A space type is a structural ceiling, not a toggle: a Client Space cannot time-gate
  • Channels: the internal chat channels this unit runs
  • Team defaults: working hours, time off, and scheduling starting points
  • Offboarding: one flow to end access, with the work product left behind
  • Membership, sessions, site grants, space grants, share links, and pending invitations each revoked and counted back
  • Access is binary, and no role hierarchy exists inside an account
Content & Consistency
  • Canvases organised by the app they render in: edit, hide, activate, delete, all versioned
  • Every canvas carries its source: company, purchased, shared, or custom
  • Restore the original of any forked canvas at any time
  • Blocks: twelve types covering SOPs, checklists, training, and documents
  • Blocks also cover forms, messaging, automations, sales, kits, recipes, budget, and construction
  • Collections targeting seven surface channels: Sites, Apps, Station, Display, Kiosks, Navigator, Workforce
  • Editing an item that is not your own forks it atomically, in one transaction
  • Receipts: a block-based designer for receipts and kitchen tickets, 80 mm or 58 mm, live thermal preview
  • Receipt blocks for logo, header, line items, totals, footer, QR, and barcode, reordered or hidden per template
  • Designs: the design-template domain Studio renders from
  • Sites: website templates applied when a new site is spun up from the Surfaces console
  • Kiosks: screen templates so every unattended terminal opens on the same flow
  • Campaigns: campaign templates authored and approved here, sent from Campaigns
  • Documents: the document-template domain Docs, Sheets, and Slides render from
  • Proposals: proposal templates instantiated by Proposals when a quote goes out
  • Forms and templates governed on the same Depot records Sign renders
  • Messaging templates approved and locked where Mail, Inbox, and Deals author them
  • Standards sync: what has been pushed to and shared with other units
  • Completeness scoring per business unit, on the home grid and the unit page
  • From Blueprint: standards land locked, stamped with their source, auto-updating unless frozen
  • From a peer: a redeemed share code gives a linked copy, and the source’s edits propagate
  • A peer share code shows once, because only its hash is stored
  • Pro Shop: browse, preview, and import marketplace listings
  • Purchased content stays linked, updates propagate from the seller, and the order is recorded
Identity & Localization
  • Identity: legal name, domain, tax ID, address, and operating hours
  • Business type: the concept types this unit operates under
  • Brand: logo, colors, and typography, defined here at no extra cost
  • Localization: currency, timezone, UI language, and guest language
  • How you operate: the operational profile the apps read from
  • Locations: every business unit on the account, managed in one view
  • Currency is a per-record fact, and no screen ever locks one
Infrastructure & Billing
  • Managed by default: files in Germany, database in France, encrypted and backed up
  • Nothing to configure to get started, and most businesses never change it
  • Bring your own database: point an organization account at your own PostgreSQL
  • Initialise your database schema from the console, not from a migration project
  • Bring your own storage: any S3-compatible provider, with files going straight to your servers
  • A connection is tested before it is committed, and health is checked on demand
  • Bad credentials surface a specific error rather than a silent failure
  • The authentication control plane stays on the managed database, so your own access is never at risk
  • Severable: every governed plane is owned by the account and can be cut out
  • The routing key naming which app renders something is never ownership, and a test fails the build if that changes
  • Semantic search runs a 1024-dimension embedding model on Calisto infrastructure
  • No catalog content is sent elsewhere to be searched, and writes carry on if the index is unavailable
  • Billing for the account, alongside the governance that sets it
What Each App Reads
  • Bookings: business hours bound schedulable time, timezone anchors open and close, currency prices folios
  • Inventory: business identity prints on purchase orders and reports, currency values stock
  • Listings: identity carries across listing pages and syndication feeds, currency prices every offer and commission
  • Registry: identity prints on member records, currency drives subscription billing, dunning, and revenue
  • Tickets: admission issues under your identity, in your currency, with your brand on passes and check-in
  • Every app in Commerce, Ops, Nexus, Interact, Work, Engage, and Create reads the same shared configuration
  • App-specific settings stay in the app, one deep link from its Purview row
  • Fifty-four apps, one definition
Honest answers

Questions about Calisto Purview

No. Purview is already running from the moment you create an account, and every Calisto app configures itself. The 53 screens are there for when you want to customise, lock something down, or expand.

Yes, and you should. Everything your team creates is saved under your business account from day one, which is the part that matters most and the part you never configure. The multi-location features are waiting for the day you need them.

Not necessarily. A business unit is a scope: a restaurant inside a hotel, a brand inside a group, a region. It is the unit configuration and reporting hang off, which is often finer than a physical site.

Add or change concept types in Purview at any time. The terminology, catalog structure and lead screens adjust across every app, and your existing data, policies and team access stay exactly as they are. You do not start over.

The write is rejected by the server with a 403, whichever app it came from. The field also stops being editable in the interface, but that part is a courtesy: the rejection is the control, and it is the same one whether the change is attempted in an app, through the API, or by an automation.

Blueprint is the headquarters layer above it. HQ locks what must stay consistent and pushes it down; Purview is where each business unit configures everything else. Blueprint pushes down, Purview configures, apps read.

One offboarding flow revokes every class of access: membership, sessions, site and space grants, share links they created, invitations still pending. Each class is revoked and counted back. Everything they created, documents, designs, customer interactions, stays with the business account.

Yes. An organization account can point at its own PostgreSQL database and its own S3-compatible storage, both tested before they are committed and health-checked afterwards. Accounts that do not bring their own run on Calisto-managed infrastructure, with files in Germany and the database in France, encrypted and backed up.

It is yours, and it leaves with you. Business units, settings, lock state and your records export in standard formats at any time, without asking anyone. An account on its own PostgreSQL and storage already holds its data on infrastructure it controls.

It is part of Core, which is included at no additional cost with a Commerce or Ops subscription and is never sold separately. The pricing section on this page reads the live catalogue and is the authority.

Yes, at 0 additional cost. Ethos is the paid brand guard that enforces it inside the editors; Purview is where the brand is declared.

Calisto Purview

Your business will grow. It might even become something new.

From one location to every location. From one currency to every currency. From one business type to whatever you become next. Everything your team creates is saved, protected and ready, whether you are scaling up or pivoting entirely.

Start using Purview