Canopy showcase, fictional data · return to /work/canopy
Canopyby DBJ TechnologiesBook a call
Ownership

Owning your install

One database, one sign-in, one deployment, all yours, with no shared infrastructure between you and anybody else. The product wears your name and your mark, with the modules you do not need switched off. And the way out is a button on the settings page, because a claim about ownership that cannot be tested is a slogan.

One codebase, your name on it

The same product runs under a different name, mark, assistant and module set on every deployment. An install is not a theme on a shared system. It is the whole system, wearing your brand, with the parts you do not need switched off.

  • The studio itself

    Canopy

    Assistant
    Dave
    Modules on
    Everything
    Sign-in
    Google
    Productiondoor answering

  • A landscape supply yard

    Yard Office

    Assistant
    Sandy
    Modules on
    HomeQuote requestsSignalsConversationsSettings
    Sign-in
    MicrosoftEmail link
    Productiondoor answering

  • A roofing contractor

    Canopy Construction

    Assistant
    Ridge
    Modules on
    HomeJobsCRMInboxMoneySettings
    Sign-in
    GoogleEmail link
    Productiondoor answering

Three invented businesses. The white-label layer is real and running; which client runs which edition is theirs to say, not mine.

Who can do what

Four tiers, assigned per person and revocable at any moment. A disabled account cannot sign in at all.

  1. Full control

    Everything, including who else gets in, the API tokens, and the webhooks.

  2. Runs the business

    Every record and every configuration surface, short of handing out access.

  3. Works the records

    Their own and unassigned records, enforced on reads and on edits. Configuration is closed.

  4. Read only

    Can browse everywhere. No control that changes anything will accept them.

What you actually receive

A source license is only real if you can run the system without me. So the engagement hands over everything needed to do exactly that.

  • The full source of your install
  • The manual, an operator guide and an administrator runbook
  • Build and deploy instructions
  • Every third-party service, and how to point each at your own account
  • The database schema, as numbered migration files
  • Every background job, what it does, and when it runs
  • Provider keys that are yours to control, not mine

The manual

25 sections, in two halves: the guide for whoever works in it, and the runbook for whoever runs it.

Operator guideAdministrator runbook

One install, one tenant

Canopy is not multi-tenant software. Your install is one database, one sign-in, one deployment, all yours, with no shared infrastructure between you and anyone else. There is no central account of mine your data passes through. That is why the ownership claim is honest: there is literally nothing to leak across customers, because there are no other customers in your install.

Leaving is a button

Every entity exports to CSV, and the whole database exports at once. The test ownership has to pass is that you can fire me and keep operating tomorrow morning, so the way out is a control on the settings page, not a support ticket.

It talks to whatever you already run

Bearer tokens for the API and signed outbound webhooks, so another system can react to what happens in here. Revoke a token the moment it is no longer needed.