Skip to main content

Appify 1.1.0 — One Complete Self-Hosted Product

Appify 1.1.0 introduces a major product and architecture update based on feedback received after the initial public release.

The original Appify 1.0.0 model separated the Admin Dashboard from the self-hosted Customer Platform source. Although both systems were designed to work together, this structure caused confusion for buyers who expected one purchase to include the complete platform.

Starting with Appify 1.1.0, the Admin Dashboard and Customer App/API are included together as one complete CodeCanyon product.

One Product and One Purchase

Appify 1.1.0 now includes:

  • Complete Appify Admin Dashboard source code

  • Complete Customer App and API source code

  • Complete public Landing Page source code

  • Visual mobile app builder

  • AI-assisted app generation

  • Flutter, WordPress, WooCommerce and WebView workflows

  • Docker build-server source

  • Shared Supabase migrations and configuration

  • Cloudflare deployment configuration

  • Vercel deployment support

  • Standard Node.js deployment support

  • Environment configuration examples

  • Installation and deployment documentation

  • Upgrade and migration documentation

A separate Customer Platform purchase is no longer required.

Existing buyers receive access to the complete combined package through the Appify 1.1.0 update.

Two Connected Projects

Appify remains organized as two connected Next.js projects:

Admin Dashboard

The Admin project contains:

  • Operator dashboard

  • Business analytics

  • Customer management

  • Subscription management

  • Plans and pricing

  • Transactions and revenue

  • Build-server management

  • Branding and white-label settings

  • Landing Page management

  • Posts and public content

  • Customer inbox

  • Platform configuration

  • Integration settings

Customer App and API

The App project contains:

  • Customer registration and authentication

  • Customer Dashboard

  • Application management

  • Visual mobile app builder

  • AI-assisted generation

  • Flutter application workflows

  • WordPress application workflows

  • WooCommerce integration

  • WebView application workflows

  • Build orchestration

  • Push notifications

  • Subscription and usage tracking

  • Customer-facing API routes

  • Generated artifact management

The projects remain separate for cleaner maintenance, independent deployment and easier scaling. They are no longer separate products.

Both projects belong to one buyer installation and are included in the same download.

Single-Buyer Self-Hosted Architecture

Appify 1.1.0 introduces a simplified single-buyer installation model.

Each installation now belongs to one CodeCanyon buyer operating one Appify-powered SaaS platform.

The previous multi-buyer hosted-platform model is no longer required for buyer installations.

The new architecture provides:

  • One buyer installation

  • One connected Admin Dashboard

  • One connected Customer App and API

  • One shared Supabase project

  • One purchase activation

  • Buyer-controlled hosting

  • Buyer-controlled customer data

  • Buyer-controlled integrations

  • Buyer-controlled build infrastructure

Internal tenant identifiers remain available for upgrade compatibility, but new installations are designed around one buyer and one connected platform.

Shared Supabase Project

The Admin and App projects now use the same buyer-owned Supabase project.

Supabase manages:

  • Administrative users

  • Customer accounts

  • Authentication

  • Application projects

  • Screens and builder data

  • Subscription plans

  • Customer subscriptions

  • Transactions

  • Build records

  • Notifications

  • Uploaded assets

  • Platform configuration

  • Branding settings

  • Integration configuration

  • Operational data

The App project includes the complete database migrations required for a new installation.

Migration 029_single_buyer_installation.sql introduces the persistent single-buyer installation identity while preserving compatibility with existing platform data.

Buyer-Owned Customer App and API

The Customer App and API are no longer provided only as a hosted platform dependency.

Buyers now deploy and control their own App project.

The Admin Dashboard connects to the buyer-owned App deployment through:

NEXT_PUBLIC_APPIFY_APP_URL

This means buyers control:

  • Customer application hosting

  • API hosting

  • Customer authentication

  • Customer data

  • Application projects

  • AI workflows

  • Build orchestration

  • Subscription usage

  • File storage

  • Custom domains

  • Platform updates

There is no production fallback to a vendor-hosted business API.

Simplified Deployment Order

The recommended Appify 1.1.0 deployment order is:

  1. Create one Supabase project

  2. Apply the App database migrations

  3. Configure and deploy the Customer App/API

  4. Verify the App status endpoint

  5. Configure the Admin Dashboard

  6. Connect Admin to the deployed App

  7. Deploy the Admin Dashboard

  8. Activate the CodeCanyon purchase

  9. Configure branding, plans and integrations

  10. Connect the Docker build server

  11. Run a complete customer and build test

The App deployment must be available before the Admin production deployment is completed.

CodeCanyon License Activation

Appify 1.1.0 uses one purchase activation for the complete connected product.

Buyers enter:

  • Their CodeCanyon purchase code

  • Their Envato purchaser email

Buyers do not configure:

  • ENVATO_PERSONAL_TOKEN

  • ENVATO_ITEM_ID

Those credentials remain private to the Appify vendor license-verification service and are never distributed with the buyer package.

The activation connects the buyer’s Admin and App installation to one licensed end product.

Standalone Docker Builder

The Docker build server is now included as a standalone archive at the root of the package:

appify-builder.zip

Buyers can upload this ZIP directly to a Linux VPS without uploading the Admin or App projects.

After extraction, the builder can be installed using Docker and connected through Admin → Builders.

The standalone builder includes:

  • Dockerfile

  • Builder server

  • Build authentication

  • Runtime assets

  • Flutter project templates

  • Visual-builder component bricks

  • Android build workflows

  • APK output

  • AAB output

  • Build logs

  • Artifact management

  • Health checks

  • Buyer setup instructions

The same builder source is also retained inside App/docker/builder/ for reference and maintenance.

Cloudflare Deployment Support

Appify 1.1.0 adds complete Cloudflare Workers deployment support for both the App and Admin projects.

The included Cloudflare configuration supports:

  • Next.js server rendering

  • API routes

  • Middleware

  • Authentication

  • Supabase sessions

  • Static assets

  • Server actions

  • Scheduled operations

  • Environment secrets

  • Custom Worker domains

  • Observability and logs

Each project includes its own Wrangler and OpenNext configuration.

Buyers can deploy using:

npm run cf:deploy

The App and Admin remain separate Cloudflare Workers connected through their public URLs.

Vercel and Node.js Compatibility

Cloudflare is not required.

Appify 1.1.0 continues to support:

  • Vercel

  • Cloudflare Workers

  • Compatible Node.js hosting

  • VPS and container deployment

  • Other compatible Next.js hosting environments

The two applications can run on the same server using separate processes and hostnames, or on completely separate hosting providers.

A common production configuration is:

  • Admin and Landing Page: www.yourdomain.com

  • Customer App and API: app.yourdomain.com

  • Docker Builder: builder.yourdomain.com

Custom Domains

Normal Admin and App domains can be configured through the selected hosting provider.

Optional customer vanity domains are supported when a complete domain provider is configured.

Cloudflare for SaaS can be used for:

  • Customer custom hostnames

  • Managed SSL certificates

  • Fallback origins

  • Customer CNAME targets

  • Domain verification

  • Certificate validation

  • Worker-based customer routing

When no custom-domain provider is configured, Appify continues working through the primary Customer App domain and hides unavailable customer-domain settings.

Environment Configuration

Environment configuration has been updated for the combined product.

The App project now owns:

  • Customer App URL

  • Supabase server configuration

  • License-server connection

  • Encryption keys

  • AI provider configuration

  • Stripe server configuration

  • OAuth configuration

  • Build-server configuration

  • Cron configuration

  • Optional custom-domain provider configuration

The Admin project now owns:

  • Admin and Landing Page URL

  • Customer App connection URL

  • Shared Supabase configuration

  • Operator configuration

  • Admin presentation settings

Legacy App API environment aliases remain available for upgrade compatibility, but new installations use NEXT_PUBLIC_APPIFY_APP_URL.

Preserved Platform Features

All major features introduced with Appify 1.0.0 remain available in the combined 1.1.0 product:

  • Business analytics

  • Customer management

  • Subscription management

  • Plans and pricing

  • Stripe billing

  • Transaction tracking

  • Build credits

  • AI-assisted app generation

  • Visual mobile app builder

  • Flutter applications

  • WordPress applications

  • WooCommerce applications

  • WebView applications

  • Android APK builds

  • Android AAB builds

  • iOS workflow support

  • Docker build servers

  • Build queues and logs

  • Push notifications

  • White-label branding

  • Public Landing Page

  • Custom domains

  • Supabase authentication

  • Customer profiles

  • Multilingual interfaces

  • RTL support

  • Posts and categories

  • Customer inbox

  • Platform notifications

  • Release notifications

  • Documentation and support resources

Updated Buyer Package

The Appify 1.1.0 package now contains:

  • Admin/

  • App/

  • appify-builder.zip

  • README-FIRST.txt

  • install-guide.txt

  • LICENSE.txt

  • documentation/documentation.pdf

  • documentation/guides/

  • Deployment documentation

  • Upgrade documentation

  • Release changelog

The package does not include:

  • Production environment files

  • Supabase service-role credentials

  • Stripe secrets

  • AI provider keys

  • OAuth secrets

  • Envato personal tokens

  • node_modules

  • Build output

  • Development caches

  • macOS metadata files

Updated Documentation

Documentation has been updated to explain:

  • The combined product model

  • The two-project architecture

  • The single-buyer installation model

  • Shared Supabase configuration

  • Required deployment order

  • App environment variables

  • Admin environment variables

  • Cloudflare deployment

  • Vercel deployment

  • Standard Node.js deployment

  • CodeCanyon activation

  • Docker builder installation

  • Custom-domain configuration

  • Upgrade procedures

  • Security recommendations

  • Production validation

  • Troubleshooting

Upgrade Notes for Existing Buyers

Existing Appify buyers receive the complete Admin and Customer App/API source through this update.

Before upgrading:

  1. Back up both source projects

  2. Back up the Supabase database

  3. Back up production environment variables

  4. Review the included changelog

  5. Review documentation/UPGRADING.md

Recommended upgrade order:

  1. Update the App project

  2. Apply only the new database migrations

  3. Verify the App status endpoint

  4. Update the Admin project

  5. Set NEXT_PUBLIC_APPIFY_APP_URL

  6. Redeploy Admin

  7. Verify authentication and sessions

  8. Verify customers, plans and subscriptions

  9. Verify AI and Stripe integrations

  10. Rebuild the Docker builder only when builder files have changed

A Clearer Product for Every Buyer

Appify 1.1.0 removes the confusion created by the previous separated-product model.

Buyers now receive the complete source code required to deploy and operate their own mobile app builder SaaS through one product and one purchase.

The Admin Dashboard and Customer App remain separate deployable projects for maintainability, but they are now included, documented and licensed together as one complete Appify installation.