Built for service businesses. Owned outright when you’re ready.
Enterprise
Your own cloud project, your own database, your own repository — so the blast radius of anything going wrong stops at your boundary instead of a shared one. Developers get seats, not the keys. Staff never hold credentials. That independence is what you keep: a dedicated environment, private hosting, GitHub-managed custom code, and the operating tools your business owns outright.
Day 1 — $2,000 one-time setup. Provisioning starts.
Day 15 — optional developer training startup: four 2-hour ONSITE sessions, $1,500 · Columbia Shuswap Regional District (Shuswap, BC)
Day 31 — monthly begins. $199 base with one developer seat, $149 per additional seat, $149 daily support.
Example: two developers with daily support = $497/month from day 31
Additional REMOTE sessions $250 per 2 hours, any time
Beta price $2,000 until 30 September 2026, then $4,000
Dedicated tenancy · unlimited admin and staff · AI and infrastructure billed to your own accounts
Owned Communications
Enterprise gives your business a private communications layer: your sending domain, your mail routing, your Firestore database, your storage bucket, and your audit trail. Leads, replies, attachments, customer history, and operational records are retained inside infrastructure you own instead of disappearing into disconnected inboxes.
Email ownership
Send and receive through your domain.
Encrypted records
Store communication history in your database.
Business continuity
Keep customer context with the company.
Private Data Layer
Email, files, records, and audit history stay with the owner.
Dedicated Control
Enterprise environments are independent deployments with their own project, their own billing, and their own operational surface. The value is ownership, not headcount.
Dedicated Environment
Enterprise runs on a completely separate Firebase project you control. No shared tenancy, no shared data, and no dependency on another operator to access your own system.
Private Hosting Platform
Your environment is deployed to your own Firebase Hosting site, your own Cloud Run function, and your own domain — managed under your Google Cloud billing.
GitHub-Managed Code
All custom code for your environment lives in a GitHub repository you own. Every change, every deploy, every module update is tracked and auditable by your team.
Enterprise Control
Admin access, user provisioning, role management, audit logging, and configuration stay under your control so the business can operate from its own in-house system.
Need your own developers working inside it? AppSite Developer starts at $199/month, including your first seat, with additional seats at $149/month each, plus a one-time setup fee — see how developer access works.
Encrypted Infrastructure
Email delivery, inbound messages, file storage, documents, and authentication all run under your project with no shared pipeline between your data and other operators.
Self-Hosted Email
SMTP/SendGrid configuration bound to your own sending domain, with inbound and outbound email records stored in your owned encrypted database.
Encrypted File Storage
Firebase Storage bucket in your own project with bucket-level ACLs, server-side encryption, and CORS policies you define.
Encrypted Documents
Firestore documents, email metadata, attachments, and operational records stay in your isolated database with no cross-tenant data exposure.
Private Auth Domain
Firebase Authentication configured under your project with your custom domain for SSO, OAuth providers, and session control.
Audit Log Ownership
All access, provisioning, and change events logged to your Firestore — not centrally aggregated by the platform.
Custom Module Config
Enable, disable, and configure each AppSite module independently for your environment and team structure.
GitHub Repository
Your environment’s custom modules, configuration, Firestore rules, deployment scripts, and integration code are all committed to a GitHub repository under your ownership. Your team reviews it, branches it, and deploys from it.
Hosting Platform
Enterprise environments deploy to a Firebase project you provision under your Google Cloud ownership, giving you full billing visibility, IAM control, quota management, and incident access without going through AppSite.
Get Started
Enterprise starts with a discovery call to scope the tools, cloud ownership, module configuration, and handoff plan your business needs in-house.
Not ready for a call yet?
The AI rollout checklist for IT managers — data access, roles, guardrails, spend allocation, hosting choice.
The moment your business has IT staff, contractors or developers working inside its systems, the question stops being what they can build and becomes what they can reach. Enterprise is built around that question. It puts your platform inside your own cloud boundary and puts deliberate layers between the people working on the system and the business running on it.
A dedicated tenancy runs in your Google Cloud organization, on projects and a billing account you own. Your data is never in a database shared with another company, and AppSite holds no standing access to your environment — we deliver software to repositories you control and you perform the deployment.
Developer access is a named grant — a seat per person, bought deliberately — not an ambient level of trust that quietly grows. Each developer works on their own branch, and that branch is enforced at deploy time rather than by convention, so one person cannot push straight to what your business is running on.
Access is decided server-side, scoped by tenant, member and role. A signed-in client cannot widen its own permissions by editing a request, because the rules that grant access never run on the client in the first place.
API keys and platform secrets stay server-side and are reached through proxies, so they are never delivered to a browser and never pasted into a config a contractor keeps. Keys are write-only once stored and rotate on a schedule.
Single sign-on issues short-lived tokens per module rather than asking people to hold a password for each one. Removing someone removes them everywhere, at once, instead of across a list of systems somebody has to remember.
The cybersecurity module scans the platform and repairs what it finds — it executes the remediation rather than handing you a PDF of issues to assign to someone. Deployments, key rotations and policy acceptances are recorded as they happen.
And the modules
Enterprise is not a security product bolted onto an empty shell. Inside that boundary sits the operating platform — the modules that track what a job costs, what was ordered, what was billed, what was paid, and what it left you with. Costs and billing are managed where the work actually happens, instead of being reconstructed from spreadsheets at month end.
Keep the accounting system you already run. AppSite handles the operating detail and hands the numbers over in a form your existing system can take.
Run it as your system of record instead. Same data, one place, nothing to reconcile between two tools that each think they are the source of truth.
The AppSite Ecosystem Stack
One path, and you can stop at any point on it. Come in through the public site, switch on the modules you need, shape them around how you actually work, let the routine parts run themselves — and when it matters enough, take the whole thing into infrastructure you own.
Below is how that is built: 14 connected layers, from public discovery and daily operations through shared modules and the control plane to dedicated tenancy. Nothing is rebuilt when you move along it — the same records, rules and history carry through.
01–03
Entry, identity, and customer participation
04–07
Work, teams, finance, and governed records
08–11
Automation, AI, connections, and devices
12–14
Shared modules, control plane, and dedicated tenants
01
ExperiencePresent AppSite as one discoverable ecosystem and turn interest into structured demand.
Includes
Result
Visitors discover the right solution and enter the platform through a clear path.
02
ExperienceEstablish who is entering, which tenant they belong to, and what they are allowed to do.
Includes
Result
Every request begins with controlled identity, tenant, and role context.
03
ExperienceGive customers, members, and other external users secure self-service access.
Includes
Result
Users participate directly instead of relying on email, calls, or manual updates.
04
Operating CoreRun the daily business from intake and customer management through delivery and reporting.
Includes
Result
Operational work is coordinated inside one connected environment.
05
Operating CoreCoordinate people, accountability, milestones, approvals, and complex delivery.
Includes
Result
Teams can see responsibility, progress, blockers, and next actions.
06
Operating CoreConnect what the business sells to what it earns, spends, purchases, and reports.
Includes
Result
Commercial and financial activity remains attached to the operation that created it.
07
Operating CoreProvide the structured, tenant-scoped source of truth used by every experience and workflow.
Includes
Result
The ecosystem shares governed records instead of duplicate spreadsheets and isolated databases.
08
IntelligenceMove repeatable work forward when records, schedules, statuses, or external events change.
Includes
Result
Routine coordination becomes consistent, traceable, and less dependent on manual follow-up.
09
IntelligenceAdd governed assistance and supervised execution without removing human accountability.
Includes
Result
Teams process information faster while retaining review, permissions, and decision authority.
10
IntelligenceConnect AppSite workflows to the external systems and communication channels the business uses.
Includes
Result
Outside systems participate in governed workflows without becoming disconnected silos.
11
IntelligenceExtend the operating model to field teams, native apps, sensors, relays, displays, and edge devices.
Includes
Result
People and physical devices can report and act from where work actually happens.
12
EcosystemDeliver reusable AppSite applications in secure multi-tenant environments.
Includes
Result
Tenants can activate capabilities quickly while preserving boundaries and a common platform model.
13
EcosystemGovern tenants, modules, compatibility, themes, environments, and provisioning from one command layer.
Includes
Result
The ecosystem remains configurable, supportable, and consistent as modules and tenants expand.
14
EcosystemPromote mature tenants into branded, isolated infrastructure without discarding shared-mode preparation.
Includes
Result
A tenant can move from shared launch to independent production while retaining AppSite standards.
One growth path
Most businesses begin with two or three modules and grow into the rest. Tell us how you work and we will map which layers you actually need — and which you can ignore for now.