{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","category":{"description":"Headless content platforms, website publishing and editorial APIs.","id":"content-management","name":"Content management \u0026 CMS"},"cloud":{"boundary":"Heroku account/team and application; platform-managed infrastructure","classificationReview":{"reviewed":"2026-11-20","source":"https://devcenter.heroku.com/articles/how-heroku-works","summary":"Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account."},"defaultBoundary":"platform-workspace","diligence":[{"reviewed":"2026-11-14","source":"https://devcenter.heroku.com/articles/private-spaces","summary":"Private Spaces provide isolated networks for dynos and selected add-ons and require an eligible verified team or Enterprise account. Review generation, region and certification scope; a general Heroku template does not establish Private Spaces compatibility.","topic":"Private Spaces"}],"id":"heroku","identity":"App/team access and configuration variables","install":"Deploy with Git, containers or app templates; configure paid dynos, database add-ons and durable file storage.","name":"Heroku","network":"Application routing; network isolation depends on the selected plan","providerType":"application-platform","reviewed":"2026-11-12","short":"Heroku","source":"https://devcenter.heroku.com/articles/how-heroku-works"},"kind":"cloud-category","listings":[{"architecture":"Apostrophe application on Heroku with MongoDB and durable asset storage.","categories":["content-management"],"category":"Content management \u0026 CMS","categoryFit":{"content-management":"Customer-operated content management and website application framework."},"cloudEvidence":[{"clouds":["heroku"],"notes":"Apostrophe application on Heroku with MongoDB and durable asset storage. The current guide initializes an Apostrophe project through its CLI. Old free-tier examples are not current price promises; Atlas and asset storage can be outside the Heroku account.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Heroku Cookbook","url":"https://apostrophecms.com/docs/cookbook/deploying-to-heroku.html","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["heroku"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/apostrophecms/apostrophe/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/apostrophecms/apostrophe"}],"summary":"The reviewed upstream contributor history includes boutell, abea, ValJed, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee."},"deploymentPaths":[{"boundary":"platform-workspace","cloud":"heroku","controlPlane":"not-assessed","evidence":[0],"operator":"customer"}],"description":"Customer-operated content management and website application framework.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Current self-hosted production guidance; not validated 100-user/1-TB HA sizing","source":"https://apostrophecms.com/docs/guide/hosting.html","status":"documented","summary":"The production guide recommends 2 GB RAM for the application plus database and 20 GB disk. It says 1 GB may suffice with a remote database or SQLite; multicore deployments need additional resources. Uploads, database growth, replicas and HA are outside that starting point."},"iac":{"artifactRef":"Current project-creation commands; pin package and database versions","artifactUrl":"https://apostrophecms.com/docs/guide/development-setup.html","reviewed":"2026-11-20","scope":"Current upstream application scaffold; production setup is separate","source":"https://apostrophecms.com/docs/guide/development-setup.html","status":"documented","summary":"The official setup and hosting guides create a project with the Apostrophe CLI and describe deploying its application with a chosen database and production process/reverse-proxy configuration. This is a custom application project, not a turnkey cloud HA template.","supportingSources":[{"title":"Production hosting configuration","url":"https://apostrophecms.com/docs/guide/hosting.html"}]},"licensePricing":{"reviewed":"2026-11-19","scope":"ApostropheCMS; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/apostrophecms/apostrophe/blob/main/packages/apostrophe/LICENSE.md","status":"documented","summary":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Upstream Passport bridge integration for the CMS login surface","source":"https://apostrophecms.com/docs/guide/custom-login-requirements.html","status":"documented","summary":"The upstream custom-login guide identifies @apostrophecms/passport-bridge for third-party single sign-on. This is a project-level module integration; configure and verify the selected Passport strategy rather than assuming every SAML/OIDC provider works out of the box."}},"id":"apostrophecms","infrastructure":["servers"],"infrastructureNotes":"Apostrophe application on Heroku with MongoDB and durable asset storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://apostrophecms.com/docs/cookbook/deploying-to-heroku.html"],"install":"Application platform deployment","installMethods":["platform-template"],"kind":"product","license":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/apostrophecms/apostrophe/blob/main/packages/apostrophe/LICENSE.md"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"ApostropheCMS","notes":"The current guide initializes an Apostrophe project through its CLI. Old free-tier examples are not current price promises; Atlas and asset storage can be outside the Heroku account.","operations":"Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Heroku Cookbook","url":"https://apostrophecms.com/docs/cookbook/deploying-to-heroku.html"},{"title":"MIT LICENSE.md","url":"https://github.com/apostrophecms/apostrophe/blob/main/packages/apostrophe/LICENSE.md"},{"title":"Releases v4.34.1","url":"https://github.com/apostrophecms/apostrophe/releases"}],"url":"https://launchinyourcloud.com/directory/apostrophecms/","website":"https://apostrophecms.com"},{"architecture":"Squidex application, database and asset storage using provider-specific instructions.","categories":["content-management"],"category":"Content management \u0026 CMS","categoryFit":{"content-management":"Self-hosted headless CMS with structured content, APIs and assets."},"cloudEvidence":[{"clouds":["aws"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"AWS EC2 Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Azure Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"GCP Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp","vendorSupport":"not-assessed"},{"clouds":["render"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Render Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render","vendorSupport":"not-assessed"},{"clouds":["heroku"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Install on Heroku | Squidex","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku","vendorSupport":"not-assessed"},{"clouds":["vultr"],"notes":"Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","reviewed":"2026-11-19","sourceType":"vendor-documentation","title":"Install on Vultr | Squidex","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-19","clouds":["aws","azure","gcp","render","heroku","vultr"],"communityAcceptance":{"reviewed":"2026-11-19","sources":[{"title":"Community, governance or adoption evidence","url":"https://github.com/Squidex/squidex/graphs/contributors"},{"title":"Upstream project","url":"https://github.com/Squidex/squidex"}],"summary":"The reviewed upstream contributor history includes SebastianStehle, kamushadenes, seamys, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[3],"operator":"customer"},{"boundary":"platform-workspace","cloud":"heroku","controlPlane":"not-assessed","evidence":[4],"operator":"customer"},{"boundary":"cloud-account","cloud":"vultr","controlPlane":"not-assessed","evidence":[5],"operator":"customer"}],"description":"Self-hosted headless CMS with structured content, APIs and assets.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Upstream deployment topology; no workload-tested minimum established","source":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-docker","status":"inconclusive","summary":"The official Compose stack establishes application, MongoDB and proxy dependencies, but no quantitative CPU/RAM/storage production floor was established in the reviewed installation materials. Confirm content volume, database replication, caches and concurrency before sizing.","supportingSources":[{"title":"Reviewed Compose services","url":"https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml"}]},"iac":{"artifactRef":"master (moving branch); Squidex major 7 / MongoDB major 6 in reviewed example","artifactUrl":"https://github.com/Squidex/squidex-hosting/tree/master/docker-compose","reviewed":"2026-11-20","scope":"Upstream Squidex 7 Compose example; assess database support and image versions separately","source":"https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml","status":"documented","summary":"The upstream hosting repository supplies a Compose stack with Squidex 7, MongoDB 6 and a Caddy proxy, persistent mounts and environment-based identity settings. These moving examples need compatible supported image versions, secrets and backups; the stack is not a replicated database/HA design."},"licensePricing":{"reviewed":"2026-11-19","scope":"Squidex; software terms only, excluding cloud charges, labour and separately licensed services","source":"https://github.com/Squidex/squidex/blob/master/LICENSE","status":"documented","summary":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms."},"release":{"releasePublishedAt":"2026-09-28T09:30:35Z","releaseTag":"7.24.0","reviewed":"2026-11-19","scope":"Squidex upstream application; verify compatibility with the selected package","source":"https://github.com/Squidex/squidex/releases/tag/7.24.0","status":"documented","summary":"Reviewed upstream 7.24.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-hosted Squidex external-provider configuration; not the deprecated Squidex.Identity server","source":"https://docs.squidex.io/id-01-getting-started/installation/external-identity-providers","status":"documented","summary":"The official external-identity guide documents configuring an external Azure AD/OAuth identity provider for self-hosted Squidex. The Compose example also exposes Google/GitHub/Microsoft credentials. The separately documented Squidex.Identity project is deprecated and must not be presented as a maintained SSO service.","supportingSources":[{"title":"Upstream Compose identity configuration","url":"https://raw.githubusercontent.com/Squidex/squidex-hosting/master/docker-compose/docker-compose.yml"}]}},"id":"squidex","infrastructure":["servers"],"infrastructureNotes":"Squidex application, database and asset storage using provider-specific instructions. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.","infrastructureReviewed":"2026-11-19","infrastructureSources":["https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2","https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure","https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp","https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render","https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku","https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr"],"install":"Application platform deployment","installMethods":["platform-template"],"kind":"product","license":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModel":"open-source","licenseModelNotes":"MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.","licenseModelSources":["https://github.com/Squidex/squidex/blob/master/LICENSE"],"licenseReviewed":"2026-11-19","model":"Fully in your account","modelLabel":"Customer-operated","name":"Squidex","notes":"The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.","operations":"Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"AWS EC2 Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-aws-ec2"},{"title":"Azure Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-azure"},{"title":"GCP Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-gcp"},{"title":"Render Guide","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-render"},{"title":"Install on Heroku | Squidex","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-heroku"},{"title":"Install on Vultr | Squidex","url":"https://docs.squidex.io/id-01-getting-started/installation/platforms/install-on-vultr"},{"title":"MIT LICENSE","url":"https://github.com/Squidex/squidex/blob/master/LICENSE"},{"title":"Releases v7.24.0","url":"https://github.com/Squidex/squidex/releases"}],"url":"https://launchinyourcloud.com/directory/squidex/","website":"https://squidex.io"}],"schemaVersion":1,"url":"https://launchinyourcloud.com/clouds/heroku/content-management/"}