Generate
Your app is assembled from the brief: website, CRM and billing, joined up and running on infrastructure you control.
Extend
Switch on capabilities and adjust your models through settings and swaps. New bespoke apps sit on top of the core rather than inside it.
Upgrade
Improvements to the shared core arrive as new versions. Migrating your data across a changed model is the coordinated step, and it's planned work with a date on it.
Regenerate or hand over
Re-emit the app as your needs change, or move operation to your own team or another agency. We hand over the project, the database and the deployment recipe, and set out the licence terms that come with it.
Proven in our own production system before it reaches yours.
Pure Creative runs its own business on Pure Stack. New capabilities are built and used there first, then promoted into the shared core, so what arrives in your deployment has already been through a real production week.
The shared core
Pure CMS and Pure CRM, maintained by us and released as versioned packages your app depends on.
Upgrades flow down
New versions reach your app on a schedule you agree to. They don't arrive silently, and they don't stop arriving.
Your customisations stay put
Your models, settings and data sit in your own project. The core beneath them improves without stepping on them.
What leaving actually involves.
Most platform pages either promise a frictionless exit or say nothing. Here is the whole picture, including the parts that cost money.
Start with what's unambiguously yours. Your data, your content, your infrastructure, and the code written specifically for you: concrete models, custom apps, theme and settings. We hand all of it over, and the data comes out of one database rather than six systems that disagree.
Your application also has nothing in it that we can switch off. Licence status is recorded for billing and visibility and is never checked at runtime, so a deployment keeps serving traffic regardless of the commercial position. That's a deliberate design decision, and it means a billing dispute can never become an outage.
What you license rather than own is the platform underneath: Pure CMS, Pure CRM, the AI suite and the generator. To keep that application patchable and rebuildable you either continue a licence, pay annual maintenance, or buy the platform outright. Ask us to quote all three before you commit to the build, and you'll never meet one as a surprise later.
The practical constraint sits at build time. Reinstalling the libraries needs a current entitlement, so an application with a lapsed licence keeps running but can't be patched, rebuilt or moved to new infrastructure until that's resolved. We'd rather describe that clearly than let you assume otherwise.
Handing operation to another team works, and we'll support it. The project is generated and documented the same way every deployment is, so a competent Django team can take it on. They'll need a Pure Stack licence of their own, or you buy the platform out first. And moving off Pure Stack entirely is a genuine migration project, because it means replacing the libraries the application is built on.
What we're responsible for
The platform
The core libraries, the generator, the deployment recipe, and the upgrades that flow through them.
The operation
Where we host and manage your deployment, we keep it running, patched and monitored. Formal service tiers are part of the managed offering we're building out, so talk to us about what you need instead of reading a tier off a page.
The relationship
Changes to your business shape become changes to your app, through the same extension points, without mounting technical debt.
The question worth asking any platform vendor is whether the application can be operated by someone else without being rebuilt. For Pure Stack the engineering answer is yes, and the commercial answer is a licence. We'll give you both in writing.
Let's talk about year three.
The interesting question is what happens when your business changes shape, and what your options look like if you ever want to move. That's the conversation we're set up for.