If you are looking at the Djangify eCommerce building and wondering:
-
What actually runs this system?
-
What is the difference between self-hosted and managed?
-
Where does Docker fit in?
-
What is a Provisioner?
-
Do I need to understand the technical side?
This article explains the structure clearly and simply.
By the end, you should understand:
-
What the main Djangify eCommerce Builder is
-
What the self-hosted version is
-
What managed hosting means
-
Where Docker is used (and where it is not)
-
How Stripe fits into everything
-
Why the system is stable
Let’s start with the most important clarification.
There Is One Core System: Djangify eCommerce Builder
Djangify eCommerce Builder (also called eBuilder) is the main system hosted on djangify.com
It is a digital eCommerce platform built to:
-
Sell downloads
-
Manage customers
-
Handle orders
-
Deliver secure files
-
Run a blog, policies pages and other content
-
Control SEO
-
Integrate with Stripe
It is built using Django and is designed specifically for digital products. Everything begins with this core application. From that foundation, there are two ways it can be used:
The software foundation is the same. The difference is who runs it and how it is delivered.
Do People Need to Understand the Whole Architecture?
In most cases, no. If you are a plumber selling downloadable guides, you do not need to understand container systems or deployment automation. This is really for anyone who is curious. What you do need to understand is:
-
Who runs the system?
-
Who maintains it?
-
Who fixes it if something goes wrong?
-
Where payments are processed?
-
Whether your store is stable and secure?
So in this article, we focus on bringing clarity and answering those questions.
The Three Layers of Djangify
To make this easy, think of Djangify in three layers:
-
The Core Application (the shop system)
-
The Hosting Model (self-hosted or managed)
-
The Payment System (Stripe)
Everything fits into one of those layers.
Layer 1: The Core Application
At its heart, Djangify eCommerce Builder is:
-
A Django application
-
A structured shop system
-
A digital download delivery engine
-
A content system
-
A secure user authentication system
This core system handles:
-
Products
-
Orders
-
Customer accounts
-
Secure file access
-
Admin management
-
SEO features
That is the engine. Now let’s look at how that engine is delivered.
Self-Hosted: You Run the Application
The self-hosted version is simple. It is:
-
A standard Django application
-
Installed on your own server
-
Managed by you
There is no Docker in the self-hosted version.
It does not include the Provisioner.
It does not include automated site creation.
It does not include infrastructure automation.
It is simply the core application that you host yourself.
You would:
-
Set up a server
-
Install Python and Django
-
Configure your environment
-
Connect Stripe
-
Run the application
You control:
-
Updates
-
Backups
-
Security patches
-
Server configuration
This option is ideal for:
-
Developers
-
Technically confident founders
-
Businesses that already manage servers
You gain full control. You take full responsibility.
Managed Hosting: We Run the Application
Managed hosting uses the same core Djangify eCommerce Builder system.
The difference is this:
You do not manage the infrastructure. We do.
This is where Docker and the Provisioner come in.
But it is important to understand that Docker is part of the main Djangify infrastructure - not part of the self-hosted version.
What Is Docker (In This Context)?
In managed hosting, Docker is used inside the Djangify infrastructure to:
-
Run each store in an isolated environment
-
Keep stores separated
-
Ensure consistent performance
-
Make deployment predictable
Think of Docker like sealed units. Each customer store runs inside its own isolated unit.
If one store has an issue, it does not affect others.
Docker is not something the managed customer needs to understand or interact with. It is an infrastructure tool used behind the scenes to make the system stable and repeatable.
What Is the Provisioner?
The Provisioner is an automation system inside the managed hosting environment.
Its job is simple:
When someone pays for managed hosting:
-
It receives confirmation from Stripe.
-
It creates a new store instance.
-
It configures it automatically.
-
It makes it accessible online.
-
It sends login details to the customer.
There is no manual setup or waiting period. You choose your store name, complete payment and your store appears. You then receive an email with your details so you can log in and get started.
The Provisioner is not part of the self-hosted version. It exists only inside the Djangify managed hosting infrastructure.
For a business owner, the important takeaway is: Managed hosting uses automation to create and manage stores reliably.
Stripe Integration: How Payments Work
Djangify connects directly to Stripe. Stripe handles:
-
Card payments
-
Fraud checks
-
Payment confirmation
-
Secure transaction processing
Here is the simple flow:
-
A customer buys your product.
-
Stripe processes the payment.
-
Stripe confirms payment to your store.
-
The system unlocks the download.
-
The order is recorded.
Stripe does not host your store. It only handles money. This applies to both self-hosted and managed hosting sites.
The difference is not in payments. The difference is in who manages the infrastructure.
Security: How It Is Handled
Security works in layers.
First, all stores run over secure HTTPS connections.
Second, user authentication is handled using established Django security practices.
Third, card details are never stored in your system. Stripe handles sensitive payment data.
In managed hosting:
-
Your storefront is isolated so if something happens to one storefront on the system it will not affect yours.
-
Infrastructure is maintained centrally.
-
Updates are applied consistently.
In self-hosted:
-
You control updates.
-
You manage server security.
-
You are responsible for applying patches.
The software foundation is secure. Responsibility differs between hosting models.
Why the System Is Stable
Stability comes from structure and simplicity. Djangify is stable because:
-
It is built on Django, which is widely used and mature.
-
The architecture is focused on digital products only.
-
It does not rely on external plugin ecosystems.
-
Stripe is a trusted payment system.
-
Managed hosting uses container isolation for consistency.
In self-hosted mode, stability depends on how well you manage your own server.
In managed mode, stability is maintained centrally.
The core application remains the same.
So Do People Need to Understand the Main Structure?
Most business owners do not need to understand:
-
Container systems
-
Infrastructure automation
-
Deployment pipelines
They need to understand:
-
What they are using
-
Who runs it
-
Who maintains it
-
How payments are handled
-
How secure it is
Developers may care about the deeper structure. Personal trainers selling health and wellness guides probably do not.
This article gives both groups clarity without overwhelming either.
Final Mental Model
Here is the simplest way to understand the Djangify eCommerce Builder:
There is one core system: Djangify eCommerce Builder.
You can use it in two ways.
Self-hosted: You install and manage the Django application yourself.
No Docker. No Provisioner. You control everything.
Managed hosting: The same core system runs inside the Djangify infrastructure.
Docker is used internally for isolation. The Provisioner automatically creates stores. We manage the servers and updates.
Stripe handles payments in both cases.
That is the structure.
In summary:
The Djangify eCommerce builder is a digital shop application.
You can run it yourself.
Or we can run it for you.
The foundation is the same.
Only the responsibility changes.
To get started with Managed Hosting CLICK HERE
If you have decided Self-Hosting is for you CLICK HERE
