Frequently asked questions

An invitation to a private GitHub repository containing the full application source, the AWS deployment configuration and the setup documentation. You provide your GitHub username at checkout and the invitation is sent to that account.

That is the whole price of the software. You will also pay Amazon for the infrastructure it runs on, which is typically $30–$500 a month depending on your size — see what it costs to run. Priority support is a separate add-on if you want it.

Yes. Teams commonly add field types, relabel the admin panel to match internal terminology, or wire the API into an existing service layer.

Keep your changes on a branch and merge upstream updates into it, rather than editing the default branch directly. That keeps git pull useful for years rather than months.

Most teams run at least a staging and a production environment from the same licence, and use spaces inside one installation for separate brands and regions.

If you are planning something unusual — deploying for clients, reselling, or running it across separate legal entities — check the licence terms in the repository, or ask us at hello@cloudsourcesoftware.com before you buy.

Work that out before you pay. Book a demo, bring your Contentful export or a description of your content model, and we will tell you honestly whether it maps. The evaluation checklist lists the cases where CloudSource is the wrong tool.

For refund terms, ask us before purchase rather than after.

Updates are pushed to the repository you have access to. Run git pull when you want them, review the changes, and redeploy on your own schedule. Nothing changes underneath you without your involvement.

Your repository access is part of the purchase. If you want certainty about how long that access lasts, or what happens with a future major version, ask us to put it in writing before you buy.

Priority support is an optional add-on covering deployment assistance, configuration help and ongoing technical questions. Scope and pricing are agreed case by case — raise it on your demo call.

Without it, you have the source, the documentation, and email contact for questions about the product itself.

You do. This is the honest cost of self-hosting, and it should weigh heavily if you do not already have people on call for your storefront.

The mitigation is architectural rather than contractual: put CloudFront in front of the API with generous cache TTLs so that published content keeps serving from the edge even if the origin has a bad night.

Not through a published API — the delivery API is read-only, and authoring happens in the admin panel. Bulk loading is handled by the import tool.

If you have a product feed that must sync automatically, raise it early. It is the most common reason a team turns out not to be a fit.

With a space per locale. Each space is fully isolated with its own models, content, media and API key, and your storefront calls /api/{space-slug}/content for the right one.

This is a different model from field-level localisation. It suits teams whose markets genuinely differ in range and merchandising, and suits teams doing straight translation less well.

Yes. It is an HTTP JSON API with CORS enabled, so anything that can make a request can read from it — server components, static site builds, mobile apps, in-store displays. There is no SDK to adopt. See the API reference for examples in JavaScript, cURL, Python and PHP.

There is no entry limit in the software, so the ceiling is whatever you size your database and application instances for. That is a very different constraint from a plan tier, and it is one you can raise by spending money on infrastructure rather than renegotiating a contract.

If you are running a very large catalogue, bring the numbers to your demo and we will talk through sizing.

It never leaves. The database is in your account and the media is in your S3 bucket. You can query the database directly, take a snapshot, or read everything through the API. There is no export request to raise with anyone.