
# ERP & CRM

Business operations, resource planning and customer relationship management.

Canonical page: https://launchinyourcloud.com/categories/erp-crm/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


Business operations, resource planning and customer relationship management.

23 listings.


## Acumatica Private Cloud ERP

Customer-operated ERP with contract billing, renewals and business records.

- Listing: https://launchinyourcloud.com/directory/acumatica/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: Windows application servers and a supported SQL Server database on customer-controlled cloud infrastructure.
- 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.
- Product website: https://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor explicitly identifies AWS and Azure private deployments separately from Acumatica SaaS. Azure Configuration Packages were retired; use supported Windows VMs and current installation requirements. Contract management here concerns billing and renewals, rather than a complete legal negotiation or signature platform. The licence permits usage reporting, which must be reviewed before assuming disconnected operation.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Windows application servers and a supported SQL Server database on customer-controlled cloud infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-operated ERP with contract billing, renewals and business records.

- contract-management: Customer-operated ERP with contract billing, renewals and business records.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.acumatica.com/blog/cloud-erp-implementation-choosing-deployment/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319 (checked 2026-11-19). 


### Cloud deployment evidence

- Private Cloud Azure/AWS (aws): https://www.acumatica.com/blog/cloud-erp-implementation-choosing-deployment/
  Windows application servers and a supported SQL Server database on customer-controlled cloud infrastructure. The vendor explicitly identifies AWS and Azure private deployments separately from Acumatica SaaS. Azure Configuration Packages were retired; use supported Windows VMs and current installation requirements. Contract management here concerns billing and renewals, rather than a complete legal negotiation or signature platform. The licence permits usage reporting, which must be reviewed before assuming disconnected operation.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Private Cloud Guide (8319) (azure): https://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319
  Windows application servers and a supported SQL Server database on customer-controlled cloud infrastructure. The vendor explicitly identifies AWS and Azure private deployments separately from Acumatica SaaS. Azure Configuration Packages were retired; use supported Windows VMs and current installation requirements. Contract management here concerns billing and renewals, rather than a complete legal negotiation or signature platform. The licence permits usage reporting, which must be reviewed before assuming disconnected operation.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Private Cloud Azure/AWS: https://www.acumatica.com/blog/cloud-erp-implementation-choosing-deployment/

- Azure Private Cloud Guide (8319): https://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319

- 2026 R2 PCS SQL Server Requirements: https://community.acumatica.com/acumatica-news-updates-2/important-update-deprecation-of-sql-server-2019-and-added-support-for-sql-server-2025-33402

- Contract Management: https://www.acumatica.com/cloud-erp-software/financial-management/contract-management/

- Contract Management Datasheet PDF: https://www.acumatica.com/media/2026/02/Contract_Management-DS-GBE.pdf

- Acumatica Agreements: https://www.acumatica.com/agreements/

- Acumatica EULA PDF: https://www.acumatica.com/media/2026/02/Acumatica-End-User-License-Agreement-January-2026.pdf

- 2026 R2 Release (Oct 2026): https://www.acumatica.com/corporate-newsroom/press-releases/acumatica-2026-r2-release-with-embedded-ai/

- 2026R2 Build Notes: https://community.acumatica.com/acumatica-news-updates-2/introducing-acumatica-cloud-erp-2026r2-37191

### Licensing sources

- https://www.acumatica.com/agreements/

- https://www.acumatica.com/media/2026/02/Acumatica-End-User-License-Agreement-January-2026.pdf

### Infrastructure sources

- https://www.acumatica.com/blog/cloud-erp-implementation-choosing-deployment/

- https://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. Acumatica ERP 2026 R2 documents Microsoft Entra ID SSO and group-to-role mapping. The Active Directory and Other External SSO feature must be enabled. This is a configured external identity integration, not an entitlement included in every licence. Scope: Acumatica ERP 2026 R2; external SSO feature, provider registration and tenant access configuration required. Source: https://beacon.acumatica.com/r/Integration-Guide/Integrating-Acumatica-ERP-with-Microsoft-Entra-ID/Integration-with-Microsoft-Entra-ID (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The 2026 R2 guide documents the AcumaticaERPInstall.msi installer and Configuration Wizard. Downloads require partner access and a selected build. This is a licensed Windows application installer, not a public IaC template; retired Azure Configuration Packages should not be reused. Scope: Acumatica ERP 2026 R2 application deployment on a separately provisioned supported server. Source: https://beacon.acumatica.com/r/Installation-Guide/Installing-Acumatica-ERP-On-Premises/Acumatica-ERP-Installation-On-Premises-To-Install-the-Acumatica-ERP-Configuration-Wizard (reviewed 2026-11-20). Deployment artifact: https://community.acumatica.com/. Artifact reference: Acumatica ERP 2026 R2; select the entitled installer build. Supporting source: Retired Azure configuration packages — https://community.acumatica.com/acumatica-news-updates-2/azure-configuration-packages-for-private-cloud-customers-8319.

- Minimum footprint / sizing: Documented. The 2026 R2 guide lists 16 GB RAM and two 3.5 GHz cores for the application server, plus a database requirement of 8 GB RAM and two 2 GHz cores. Its small disk baselines exclude workload growth; production uses a supported server OS. Scope: Version-specific application/database requirements; not a complete 1 TB HA deployment or performance guarantee. Source: https://beacon.acumatica.com/r/Installation-Guide/System-Requirements-for-the-Acumatica-ERP-Installation?contentId=a0hF3ukKGMcMMAAO9NbHXA (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Acumatica Private Cloud ERP; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.acumatica.com/agreements/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Apache OFBiz

Apache enterprise resource planning and commerce application framework.

- Listing: https://launchinyourcloud.com/directory/apache-ofbiz/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: OFBiz JVM application and database in an AWS container delivery package.
- 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.
- Product website: https://ofbiz.apache.org/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Yobitel publishes the AWS package. Its 3.4.01 label is a packaging version, not an Apache OFBiz release. Verify the contained OFBiz version and upstream security fixes before production. Apache currently publishes 24.09.08 and recommends the latest stable branch; the repackager label does not establish that its image contains this release.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

OFBiz JVM application and database in an AWS container delivery package. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Apache enterprise resource planning and commerce application framework.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-j7a5gcbjzd6vu (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-j7a5gcbjzd6vu
  OFBiz JVM application and database in an AWS container delivery package. Yobitel publishes the AWS package. Its 3.4.01 label is a packaging version, not an Apache OFBiz release. Verify the contained OFBiz version and upstream security fixes before production.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes JacquesLeRoux, jacopoc, eigood, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/apache/ofbiz-framework/graphs/contributors

- Upstream project: https://github.com/apache/ofbiz-framework

### Sources

- AWS Marketplace: https://aws.amazon.com/marketplace/pp/prodview-j7a5gcbjzd6vu

- GitHub LICENSE (Apache-2.0): https://raw.githubusercontent.com/apache/ofbiz-framework/trunk/LICENSE

- GitHub Commits: https://github.com/apache/ofbiz-framework/commits/trunk

- Official OFBiz releases and update guidance: https://ofbiz.apache.org/download.html

### Licensing sources

- https://raw.githubusercontent.com/apache/ofbiz-framework/trunk/LICENSE

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-j7a5gcbjzd6vu


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. The reviewed AWS offer delivers Container image from Yobitel. Its package version is 3.4.01; verify the contained application and required entitlements separately. Scope: Apache OFBiz selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-j7a5gcbjzd6vu (reviewed 2026-11-19). Offer prodview-j7a5gcbjzd6vu: Yobitel; Container image; package 3.4.01; https://aws.amazon.com/marketplace/pp/prodview-j7a5gcbjzd6vu.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed upstream installation documentation does not establish a supported external SAML/OIDC user-login configuration for the selected OFBiz application. Java security components, LDAP references or custom integrations alone are insufficient to claim a supported federation path. Scope: Apache OFBiz core; supported release, external IdP and required plugin/configuration remain to be confirmed. Source: https://github.com/apache/ofbiz-framework/blob/trunk/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. OFBiz publishes a Dockerfile and a guide for building the runtime from downloaded source, with separate seed/demo initialization and plugin handling. Pin a supported source release and configure database, durable data and credentials; the default demo quick start is not a production HA recipe. Scope: Reviewed OFBiz source-built runtime container; trunk is moving and is not a supported-release guarantee. Source: https://github.com/apache/ofbiz-framework/blob/trunk/DOCKER.adoc (reviewed 2026-11-20). Deployment artifact: https://github.com/apache/ofbiz-framework/blob/trunk/Dockerfile. Artifact reference: trunk (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed README and Docker guide specify the Java/build environment and runtime packaging but do not establish a quantitative whole-stack CPU/RAM/storage minimum. JVM heap settings alone would not size the database, jobs, storage and production replicas. Scope: Apache OFBiz supported-release deployment; reviewed trunk prerequisites are not a 100-user HA benchmark. Source: https://github.com/apache/ofbiz-framework/blob/trunk/README.md (reviewed 2026-11-20). Supporting source: Container runtime guide — https://github.com/apache/ofbiz-framework/blob/trunk/DOCKER.adoc.

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Apache OFBiz; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/apache/ofbiz-framework/trunk/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Atomic CRM

Customer-operated CRM for contacts, companies, deals and communication history.

- Listing: https://launchinyourcloud.com/directory/atomic-crm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image
- Architecture: Atomic CRM frontend and a complete self-hosted Supabase backend on an Azure VM.
- 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.
- Product website: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.atomic-crm
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The cloudimg package includes local backend services; using hosted Supabase would create a different data boundary. Do not transfer hosted-service attestations.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Atomic CRM frontend and a complete self-hosted Supabase backend on an Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-operated CRM for contacts, companies, deals and communication history.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.atomic-crm (checked 2026-11-19). 


### Cloud deployment evidence

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.atomic-crm
  Atomic CRM frontend and a complete self-hosted Supabase backend on an Azure VM. The cloudimg package includes local backend services; using hosted Supabase would create a different data boundary. Do not transfer hosted-service attestations.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes fzaninotto, slax57, nawan-b, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/marmelab/atomic-crm/graphs/contributors

- Upstream project: https://github.com/marmelab/atomic-crm

### Sources

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.atomic-crm

- GitHub LICENSE.md (MIT): https://raw.githubusercontent.com/marmelab/atomic-crm/main/LICENSE.md

- GitHub Commits: https://github.com/marmelab/atomic-crm/commits/main

### Licensing sources

- https://raw.githubusercontent.com/marmelab/atomic-crm/main/LICENSE.md

### Infrastructure sources

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.atomic-crm


### Buyer diligence


Research coverage: 7/12 fields (58%); 7 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: Atomic CRM selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.atomic-crm?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.atomic-crm: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.atomic-crm.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: cloudimg1647283583153.atomic-crm public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.atomic-crm?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Documented. Atomic CRM documents SAML 2.0 sign-in through Supabase Auth. Supabase also publishes a self-hosted SAML setup requiring signing keys, Auth settings and registered IdP metadata. Configure the CRM login path and matching backend version; the hosted Supabase console instructions alone do not configure a local backend. Scope: Atomic CRM with a configured self-hosted Supabase Auth backend; provider-image defaults are not assumed. Source: https://marmelab.com/atomic-crm/doc/developers/sso/ (reviewed 2026-11-20). Supporting source: Self-hosted Supabase SAML configuration — https://supabase.com/docs/guides/self-hosting/self-hosted-saml-sso.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The production guide deploys Supabase schema/functions separately from the built static frontend. For customer-owned infrastructure, deploy the complete self-hosted Supabase backend and apply CRM migrations/functions; hosting only the frontend while using hosted Supabase changes the data boundary. Scope: Atomic CRM upstream deployment; Azure publisher packaging has a separate version and operations model. Source: https://marmelab.com/atomic-crm/doc/developers/deploy/ (reviewed 2026-11-20). Deployment artifact: https://github.com/marmelab/atomic-crm. Artifact reference: main (moving branch); match the selected CRM release to its migrations and backend configuration. Supporting source: Complete self-hosted backend deployment — https://supabase.com/docs/guides/self-hosting/docker.

- Minimum footprint / sizing: Documented. The underlying self-hosted Supabase Docker guide lists a minimum of 4 GB RAM, two CPU cores and 40 GB SSD, recommending 8 GB, four cores and 80 GB or more. This is a backend baseline only; CRM functions, attachments, frontend hosting, backups and HA need additional workload sizing. Scope: Supabase platform floor supporting Atomic CRM; not a validated CRM or Azure image minimum for 100 users and 1 TB. Source: https://supabase.com/docs/guides/self-hosting/docker (reviewed 2026-11-20). Supporting source: CRM backend/frontend deployment boundary — https://marmelab.com/atomic-crm/doc/developers/deploy/.

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Atomic CRM; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/marmelab/atomic-crm/main/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v2.0.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Atomic CRM upstream application; verify compatibility with the selected package. Source: https://github.com/marmelab/atomic-crm/releases/tag/v2.0.0 (reviewed 2026-11-19).







## AureusERP

Customer-operated ERP for business, inventory, purchasing and financial records.

- Listing: https://launchinyourcloud.com/directory/aureuserp/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: VM image; Docker / Compose
- Architecture: Laravel application, PostgreSQL, file storage and workers.
- 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.
- Product website: https://aureuserp.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Hostinger and cloudimg provide separate packages. Check the installed application version and licence before applying upstream changes.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Laravel application, PostgreSQL, file storage and workers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-operated ERP for business, inventory, purchasing and financial records.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/aureuserp (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.aureuserp-ubuntu-24-04 (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/aureuserp
  Laravel application, PostgreSQL, file storage and workers. Hostinger and cloudimg provide separate packages. Check the installed application version and licence before applying upstream changes.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Microsoft Marketplace (azure): https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.aureuserp-ubuntu-24-04
  Laravel application, PostgreSQL, file storage and workers. Hostinger and cloudimg provide separate packages. Check the installed application version and licence before applying upstream changes.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jitendra-webkul, suraj-webkul, sandeep-webkul, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/aureuserp/aureuserp/graphs/contributors

- Upstream project: https://github.com/aureuserp/aureuserp

### Sources

- Hostinger: https://www.hostinger.com/applications/aureuserp

- Microsoft Marketplace: https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.aureuserp-ubuntu-24-04

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/aureuserp/aureuserp/master/LICENSE

- GitHub Releases: https://github.com/aureuserp/aureuserp/releases

### Licensing sources

- https://raw.githubusercontent.com/aureuserp/aureuserp/master/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/aureuserp

- https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.aureuserp-ubuntu-24-04


### Buyer diligence


Research coverage: 7/12 fields (58%); 5 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance. Scope: AureusERP selected Azure public offer. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.aureuserp-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19). Offer cloudimg1647283583153.aureuserp-ubuntu-24-04: cloudimg; Virtual machine; https://marketplace.microsoft.com/en-gb/product/cloudimg1647283583153.aureuserp-ubuntu-24-04.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed Microsoft public-offer catalog sets isMacc to false. This finding applies to this software offer, not separately billed Azure infrastructure or another negotiated agreement. Scope: cloudimg1647283583153.aureuserp-ubuntu-24-04 public offer, reviewed 2026-11-19. Source: https://catalogapi.azure.com/offers/cloudimg1647283583153.aureuserp-ubuntu-24-04?api-version=2021-10-01&market=US&language=en (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed AureusERP README documents local administration and role/permission setup, but does not establish an external SAML/OIDC user-login provider for the self-hosted core. Laravel, Filament and role-management dependencies alone do not establish SSO support. Scope: AureusERP self-hosted core; optional plugins require their own supported-version and entitlement evidence. Source: https://github.com/aureuserp/aureuserp/blob/master/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream README provides a Composer/source installation and php artisan erp:install to create the environment, schema, roles and admin account. Its quick start and Sail Compose file are development-oriented; they do not establish a hardened production or HA deployment. Scope: Reviewed AureusERP application bootstrap; provision production web/database services separately. Source: https://github.com/aureuserp/aureuserp/blob/master/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/aureuserp/aureuserp. Artifact reference: master (moving branch). Supporting source: Sail development Compose configuration — https://github.com/aureuserp/aureuserp/blob/master/docker-compose.yml.

- Minimum footprint / sizing: Sources checked — unresolved. The README specifies PHP, database and web-server compatibility, but no quantitative whole-stack CPU/RAM/storage floor. Its development requirements and Sail configuration do not validate the selected modules for the proposed production workload. Scope: AureusERP application, selected plugins, database, queues and storage; production sizing remains unconfirmed. Source: https://github.com/aureuserp/aureuserp/blob/master/README.md (reviewed 2026-11-20).

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: AureusERP; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/aureuserp/aureuserp/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v1.8.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: AureusERP upstream application; verify compatibility with the selected package. Source: https://github.com/aureuserp/aureuserp/releases/tag/v1.8.0 (reviewed 2026-11-19).







## Bigcapital

Self-hosted accounting, invoicing and financial reporting application.

- Listing: https://launchinyourcloud.com/directory/bigcapital/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: Application services, database and persistent accounting documents.
- 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.
- Product website: https://bigcapital.app
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Accounting software does not by itself establish local tax certification or payroll compliance.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Application services, database and persistent accounting documents. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Self-hosted accounting, invoicing and financial reporting application.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/bigcapital (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/bigcapital
  Application services, database and persistent accounting documents. Accounting software does not by itself establish local tax certification or payroll compliance.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes abouolia, elforjani13, jsoref, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/bigcapitalhq/bigcapital/graphs/contributors

- Upstream project: https://github.com/bigcapitalhq/bigcapital

### Sources

- Hostinger: https://www.hostinger.com/applications/bigcapital

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/bigcapitalhq/bigcapital/develop/LICENSE

- GitHub Releases: https://github.com/bigcapitalhq/bigcapital/releases

### Licensing sources

- https://raw.githubusercontent.com/bigcapitalhq/bigcapital/develop/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/bigcapital


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The upstream Google authentication guide implements server-side OAuth 2.0 sign-in and sign-up, with the button enabled only when the backend provider is configured. This establishes Google login, not generic SAML federation or SCIM. Scope: Reviewed Bigcapital develop branch; Google OAuth client, backend settings and correct redirect origin required. Source: https://github.com/bigcapitalhq/bigcapital/blob/develop/docs/google-auth.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Docker deployment guide uses a production Compose file and pre-built registry images, with environment configuration and database migration steps. Pin compatible code/images and provide secrets, durable data, TLS and backups; the recipe does not establish HA. Scope: Self-hosted Bigcapital production Compose deployment; guide and moving source branches must be version-matched. Source: https://docs.bigcapital.app/deployment/docker (reviewed 2026-11-20). Deployment artifact: https://github.com/bigcapitalhq/bigcapital/blob/develop/docker-compose.prod.yml. Artifact reference: develop (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The production Compose recipe identifies multiple application and data services but does not specify quantitative CPU/RAM/storage reservations or a tested full-stack minimum. Size its databases, queues, workers and durable data together for the intended accounting workload. Scope: Reviewed Bigcapital production Compose source; service count alone is not a 100-user or HA capacity claim. Source: https://github.com/bigcapitalhq/bigcapital/blob/develop/docker-compose.prod.yml (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Bigcapital; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/bigcapitalhq/bigcapital/develop/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v0.25.46 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Bigcapital upstream application; verify compatibility with the selected package. Source: https://github.com/bigcapitalhq/bigcapital/releases/tag/v0.25.46 (reviewed 2026-11-19).







## Celerp

Source-available customer-operated business, inventory and ERP application.

- Listing: https://launchinyourcloud.com/directory/celerp/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Business Source License 1.1 with an internal-business production grant; commercial hosted resale needs separate permission.
- Licensing model: source-available
- Installation: VM image
- Architecture: Celerp application, database and persistent business records on a DigitalOcean Droplet.
- 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.
- Product website: https://marketplace.digitalocean.com/apps/celerp
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The BSL-1.1 additional grant permits internal business production use, while hosted resale and white-label offerings need separate commercial permission. Current releases and contributor history establish an actively developed young project; they do not guarantee production capacity or a support SLA.

Business Source License 1.1 with an internal-business production grant; commercial hosted resale needs separate permission.

Celerp application, database and persistent business records on a DigitalOcean Droplet. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Source-available customer-operated business, inventory and ERP application.

### Deployment boundaries


- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://marketplace.digitalocean.com/apps/celerp (checked 2026-11-19). 


### Cloud deployment evidence

- DO Marketplace (digitalocean): https://marketplace.digitalocean.com/apps/celerp
  Celerp application, database and persistent business records on a DigitalOcean Droplet. The BSL-1.1 additional grant permits internal business production use, while hosted resale and white-label offerings need separate commercial permission. Current releases and contributor history establish an actively developed young project; they do not guarantee production capacity or a support SLA.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- DO Marketplace: https://marketplace.digitalocean.com/apps/celerp

- GitHub LICENSE (BSL-1.1): https://raw.githubusercontent.com/celerp/celerp/main/LICENSE

- GitHub Commits: https://github.com/celerp/celerp/commits/main

### Licensing sources

- https://raw.githubusercontent.com/celerp/celerp/main/LICENSE

### Infrastructure sources

- https://marketplace.digitalocean.com/apps/celerp


### Buyer diligence


Research coverage: 5/12 fields (42%); 3 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed self-hosted README describes application setup and login, but does not establish a supported external SAML/OIDC user-login integration. Business-service connectors and application API authentication are not evidence of identity-provider federation. Scope: Reviewed Celerp source distribution; provider, version and login surface still require confirmation. Source: https://github.com/celerp/celerp/blob/main/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Celerp documents native packages and a pip installation with celerp init, plus a headless service path using celerp start. Initialization can reuse an existing PostgreSQL server or start a bundled one. This is application installation, not a complete production cloud/HA template. Scope: Reviewed Celerp application and database initialization; service operation, network access and backups require configuration. Source: https://github.com/celerp/celerp/blob/main/README.md (reviewed 2026-11-20). Deployment artifact: https://github.com/celerp/celerp. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Sources checked — unresolved. The README describes a bundled or external PostgreSQL server and headless operation, but does not establish a quantitative CPU/RAM/storage minimum or an HA profile. The desktop installer being able to serve an office is not a benchmark for the proposed workload. Scope: Reviewed Celerp application plus PostgreSQL; data volume, concurrent users and redundancy require sizing. Source: https://github.com/celerp/celerp/blob/main/README.md (reviewed 2026-11-20).

- License pricing: Edition-dependent. Business Source License 1.1 with an internal-business production grant; commercial hosted resale needs separate permission. Scope: Celerp; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/celerp/celerp/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v2.9.0 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Celerp upstream application; verify compatibility with the selected package. Source: https://github.com/celerp/celerp/releases/tag/v2.9.0 (reviewed 2026-11-19).







## Creatio Customer-Managed

Customer-managed business application platform with sales, orders and contract records.

- Listing: https://launchinyourcloud.com/directory/creatio/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: Creatio application servers and a supported database, with documented AWS and Azure configurations.
- 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.
- Product website: https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The general deployment procedure names additional clouds, while the detailed system matrix specifically identifies AWS and Azure and qualifies other infrastructure. The reviewed badges follow the concrete matrix; named-user, server and product entitlements remain separate. Contract administration is part of the configured sales workflow.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Creatio application servers and a supported database, with documented AWS and Azure configurations. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-managed business application platform with sales, orders and contract records.

- contract-management: Customer-managed business application platform with sales, orders and contract records.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements (checked 2026-11-19). 


### Cloud deployment evidence

- Customer-Managed Deployment (aws): https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure
  Creatio application servers and a supported database, with documented AWS and Azure configurations. The general deployment procedure names additional clouds, while the detailed system matrix specifically identifies AWS and Azure and qualifies other infrastructure. The reviewed badges follow the concrete matrix; named-user, server and product entitlements remain separate. Contract administration is part of the configured sales workflow.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- System Requirements (azure): https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements
  Creatio application servers and a supported database, with documented AWS and Azure configurations. The general deployment procedure names additional clouds, while the detailed system matrix specifically identifies AWS and Azure and qualifies other infrastructure. The reviewed badges follow the concrete matrix; named-user, server and product entitlements remain separate. Contract administration is part of the configured sales workflow.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Customer-Managed Deployment: https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure

- System Requirements: https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements

- Contracts Guide: https://academy.creatio.com/guides/creatio-apps/products/sales-tools/orders-and-invoices/create-contract

- Creatio Licensing Overview: https://academy.creatio.com/guides/setup-and-administration/administration/licensing/creatio-licensing

- Licensing FAQ: https://academy.creatio.com/guides/setup-and-administration/administration/licensing/creatio-licensing-faq

- 8.3.4 Twin Release Notes (May 2026): https://academy.creatio.com/guides/resources/release-notes/8-3-4-twin-release-notes

- 10.1 Unlimited Release Notes: https://academy.creatio.com/guides/resources/release-notes/10-1-unlimited-release-notes

- AI Studio Oct 2026: https://academy.creatio.com/guides/ai-studio/release-notes/october-2026/ai-studio-2026-10-22-release-notes

### Licensing sources

- https://academy.creatio.com/guides/setup-and-administration/administration/licensing/creatio-licensing

- https://academy.creatio.com/guides/setup-and-administration/administration/licensing/creatio-licensing-faq

### Infrastructure sources

- https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure

- https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Creatio 10 documents Microsoft Entra ID SAML sign-in with metadata exchange, application endpoint configuration and optional just-in-time provisioning. Configure the external identity provider and Creatio instance; LDAP synchronization is a separate capability. Scope: Creatio 10 customer-managed application; version-specific SAML and mobile SSO settings apply. Source: https://academy.creatio.com/guides/setup-and-administration/administration/user-and-access-management/authentication/set-up-sso-via-azure-ad (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor documents customer-managed Windows/IIS and Linux/.NET deployments, with separate database, Redis and application-server setup. This establishes an installation procedure, not a complete public Terraform or Helm deployment. Obtain the licensed setup files and follow the selected platform guide. Scope: Creatio 10 customer-managed cloud/on-site installation; infrastructure and optional components are separate. Source: https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/general-creatio-deployment-procedure (reviewed 2026-11-20). Supporting source: Server requirements — https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements.

- Minimum footprint / sizing: Sources checked — unresolved. The vendor provides a requirements calculator that depends on application, platform, database and active-user choices. The reviewed requirements do not establish a single quantitative whole-stack floor for the proposed workload; mail-listener or network figures are not application-server sizing. Scope: Creatio customer-managed application, database, Redis and selected optional services; workload and HA inputs required. Source: https://academy.creatio.com/resources/system-requirements-calculator (reviewed 2026-11-20). Supporting source: Server-side requirements — https://academy.creatio.com/guides/setup-and-administration/on-site-deployment/system-requirements/server-side-system-requirements.

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Creatio Customer-Managed; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://academy.creatio.com/guides/setup-and-administration/administration/licensing/creatio-licensing (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## ERPNext Supplier Management

Self-hosted supplier records, procurement documents, quotation attachments and supplier scorecards.

- Listing: https://launchinyourcloud.com/directory/erpnext-supplier-management/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPL-3.0; implementation and support separately arranged
- Licensing model: open-source
- Installation: Frappe installation scripts
- Architecture: Customer-operated ERP application and database
- Operations: Customer or implementation partner operates the application and maintains backups and upgrades.
- Product website: https://frappe.io/erpnext
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

An adjacent procurement comparator: supplier records connect RFQs, quotations, orders, receipts and invoices; source quotations can be retained as attachments. Supplier scorecards support recurring performance evaluation. The reviewed sources do not establish turnkey certificate-of-insurance expiry or supplier-compliance document workflows. ERPNext advisory GHSA-cc74-rc2g-p7hw describes authenticated SQL injection in the Selling and Buying modules that can expose sensitive database and active-session data, enabling administrator account takeover. There is no workaround; upgrade to 15.121.6 or 16.37.0 or later. ERPNext v16.60.0 adds supplier and customer dashboards plus RFQ and account-dimension changes, and includes portal and permission hardening. Review custom supplier workflows and permissions before upgrading.

The listed supplier-management functionality is part of ERPNext, whose official repository uses GPLv3. Commercial hosting, implementation or support services do not convert that application code into an open-core offering.

The listed self-hosted installation uses application servers, database services or container workloads. This classification covers that deployment option; managed storage or a vendor control plane does not make the application serverless.


### Category fit

- vendor-supplier-document-management: An adjacent procurement comparator covering supplier records, quotation attachments and recurring scorecards; turnkey supplier certification and insurance-expiry workflows were not verified.

- erp-crm: Supplier and procurement records within the ERPNext suite, connecting quotations, orders, receipts and invoices. This listing focuses on that ERP workflow.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/erpnext--erp-next (checked 2026-11-12). Source: https://github.com/gridalpha/erpnext-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- ERPNext self-hosted deployment on Railway (railway): https://railway.com/deploy/erpnext--erp-next
  The community recipe runs ERPNext with web, queue, scheduler and realtime services plus MariaDB and Redis in a customer project. It layers Railway-specific startup/storage handling over the upstream ERPNext v16 image. Supplier management is part of that ERPNext application; review versions, backups and integrations separately from vendor-hosted Frappe Cloud.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the ERPNext Railway image (railway): https://github.com/gridalpha/erpnext-railway/blob/main/Dockerfile
  The inspected community wrapper starts from frappe/erpnext:v16 and adapts process supervision and persisted site assets for Railway. Match the selected ERPNext/Frappe release and database requirements before deployment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosting and licensing: https://frappe.io/erpnext/pricing

- Supplier records and linked documents: https://docs.frappe.io/erpnext/supplier

- Supplier quotation attachments: https://docs.frappe.io/erpnext/supplier-quotation

- Supplier scorecards: https://docs.frappe.io/erpnext/supplier-scorecard

- Licensing and edition terms: https://raw.githubusercontent.com/frappe/erpnext/develop/license.txt

- Licensing and edition terms: https://docs.frappe.io/legal/others/license-and-trademark

- ERPNext Selling and Buying SQL-injection advisory: https://github.com/frappe/erpnext/security/advisories/GHSA-cc74-rc2g-p7hw

- ERPNext v16.60.0 release: https://github.com/frappe/erpnext/releases/tag/v16.60.0

- ERPNext cross-scope data advisory: https://github.com/frappe/erpnext/security/advisories/GHSA-m668-9q43-8g29

- ERPNext supplier invoice exposure advisory: https://github.com/frappe/erpnext/security/advisories/GHSA-9jrr-9pr6-7mv8

### Licensing sources

- https://raw.githubusercontent.com/frappe/erpnext/develop/license.txt

- https://docs.frappe.io/legal/others/license-and-trademark

- https://frappe.io/erpnext/pricing

### Infrastructure sources

- https://frappe.io/erpnext/pricing


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Frappe documents OIDC-based social login between a Frappe identity-provider server and an application server. Configure the framework clients and review user-role mapping; this is not a supplier-module-specific identity guarantee. Scope: ERPNext/Frappe platform authentication; business-module authorization is separate. Source: https://docs.frappe.io/framework/user/en/guides/integration/openid_connect_and_frappe_social_login (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: ERPNext advisories cover cross-scope business-data access and public supplier e-invoice exposure. Upgrade to a fixed or later supported ERPNext release and recheck supplier, invoice, and cross-company permissions. Scope: GHSA-m668-9q43-8g29 is fixed in 15.124.2 and 16.53.0; GHSA-9jrr-9pr6-7mv8 is fixed in 15.124.0 and 16.52.0.. Source: https://github.com/frappe/erpnext/security/advisories/GHSA-m668-9q43-8g29 (reviewed 2026-11-18). Supporting source: Supplier e-invoice advisory — https://github.com/frappe/erpnext/security/advisories/GHSA-9jrr-9pr6-7mv8.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Frappe Docker provides a production Compose base and deployment overrides. Its pwd.yml is a disposable demo. Build/select the ERPNext image and matching configuration; this is platform packaging, not a separately versioned supplier-management appliance. Scope: ERPNext platform deployment; supplier-management configuration remains application-specific. Source: https://github.com/frappe/frappe_docker (reviewed 2026-11-14). Deployment artifact: https://github.com/frappe/frappe_docker. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. The official Frappe Docker single-server ERPNext example recommends two vCPUs, 4 GB RAM and 50 GB SSD, with MariaDB, Redis and an HTTPS proxy on that host. This is a small single-bench recipe, not a validated supplier-management capacity or HA minimum for 100 users and 1 TB. Scope: Underlying ERPNext/Frappe single-server example; additional data, workers, backups and replicas require sizing. Source: https://github.com/frappe/frappe_docker/blob/main/docs/02-setup/08-single-server-nginxproxy-example.md (reviewed 2026-11-20).

- License pricing: Documented. ERPNext is free open-source software under GPLv3. Self-hosting does not require a per-user software subscription; hosting, implementation and support are separate costs. Frappe Cloud prices are managed-hosting prices, not self-hosted licence fees. Scope: ERPNext core, including supplier-management functionality; third-party apps and services have separate terms. Source: https://frappe.io/erpnext/pricing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. ERPNext v16.60.0 was published November 17, 2026. It adds supplier and customer dashboards, RFQ and account-dimension changes, and portal and permission hardening; validate custom workflows and installed Frappe compatibility. Scope: Upstream ERPNext v16 release. Source: https://github.com/frappe/erpnext/releases/tag/v16.60.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- ERPNext Selling and Buying SQL injection (security-advisory): GHSA-cc74-rc2g-p7hw permits database and active-session disclosure, with possible administrator account takeover. Scope: ERPNext Selling/Buying: fixed in 15.121.6 and 16.37.0. This is a platform-module issue, not a separately versioned supplier appliance. Conditions: An authenticated account, including a portal account without assigned roles, can reach the vulnerable endpoint; no victim interaction is required. Action: Install a fixed or later supported patch for the deployed branch. The advisory provides no workaround. Source: https://github.com/frappe/erpnext/security/advisories/GHSA-cc74-rc2g-p7hw; reviewed 2026-11-17.

- ERPNext supplier and business-data access-control fixes (security-advisory): ERPNext advisories cover cross-scope business-data access and public supplier e-invoice exposure. Scope: GHSA-m668-9q43-8g29 is fixed in 15.124.2 and 16.53.0; GHSA-9jrr-9pr6-7mv8 is fixed in 15.124.0 and 16.52.0. Conditions: The first issue requires a low-privilege authenticated user. The invoice issue concerns affected public portal behavior. Action: Upgrade to a fixed or later supported ERPNext release and recheck supplier, invoice, and cross-company permissions. Source: https://github.com/frappe/erpnext/security/advisories/GHSA-m668-9q43-8g29; reviewed 2026-11-18. Supporting source: Supplier e-invoice advisory — https://github.com/frappe/erpnext/security/advisories/GHSA-9jrr-9pr6-7mv8.




## EspoCRM Self-Hosted

Self-hosted CRM with sales records, customer-service features and email campaign management.

- Listing: https://launchinyourcloud.com/directory/espocrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 core; commercial extensions use separate restricted terms
- Licensing model: open-source
- Installation: Official Docker, installation script or manual PHP server installation
- Architecture: Persistent PHP API/web application and relational database; official Docker setup includes separate database and background-daemon services.
- Operations: Customer maintains application/database containers or servers, scheduled work, email services, backups, upgrades and selected extension compatibility.
- Product website: https://www.espocrm.com/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-16

### Scope and qualifications

The core includes campaign management. The feature matrix places BPM and workflows in Advanced Pack, while sales/inventory functions are in Sales Pack. These paid extensions have separate license terms and should not be assumed to be part of the AGPL core. EspoCRM 10.1.2 fixes OAuth Server access tokens being rejected when 2FA is enabled and an administrator temporarily losing access to scopes after another administrator views that user's record access. Operators using OAuth or 2FA should update.

The downloadable core is GNU AGPL version 3. Advanced Pack and other commercial extensions use a separate license restricting redistribution and limiting installation/use. The directory groups open-source and open-core offerings under one filter.

Persistent PHP API/web application and relational database; official Docker setup includes separate database and background-daemon services. EspoCRM 10.1 drops support for MariaDB 10.3–10.5, so upgrades require a supported database version.


### Category fit

- erp-crm: Customer relationship management for accounts, contacts, leads and sales opportunities; broader ERP functions are not established for the base application.

- marketing-automation: Segmented campaign email, target lists and campaign tracking; workflow/BPM automation is separately offered in Advanced Pack.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/espocrm (checked 2026-11-12). 


### Cloud deployment evidence

- EspoCRM self-hosted deployment on Railway (railway): https://railway.com/deploy/espocrm
  The community template deploys the official espocrm/espocrm image with PostgreSQL and persistent application files in the customer project. Review the selected release, background job configuration, email and backups. Paid workflow or other commercial extensions are not established by this core application deployment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release feed publishes EspoCRM 10.1.2 dated November 16, 2026. The vendor documents named Red Cross implementations, including the Armenian Red Cross Society and Slovak Red Cross, with links to institutional sources. Those implementations demonstrate adoption without establishing one common hosting model or extension set.

Reviewed 2026-11-16.

- Current maintained download and release: https://www.espocrm.com/download/

- Named institutional adoption examples: https://www.espocrm.com/blog/nonprofits-espocrm/

- EspoCRM 10.1.2 authentication and access fixes: https://github.com/espocrm/espocrm/releases/tag/10.1.2

### Sources

- Self-hosted installation, current release and core license: https://www.espocrm.com/download/

- Core and extension feature boundaries: https://www.espocrm.com/features/

- Campaign configuration and email delivery: https://docs.espocrm.com/user-guide/campaigns/

- Open-source application license: https://www.espocrm.com/espocrm-open-source-license/

- Commercial extension restrictions: https://www.espocrm.com/extension-license-agreement/

- Named nonprofit implementations: https://www.espocrm.com/blog/nonprofits-espocrm/

- Application architecture and database requirements: https://github.com/espocrm/espocrm

- EspoCRM 10.1 compatibility changes: https://www.espocrm.com/blog/espocrm-v10-1-released/

- EspoCRM 10.1.2 authentication and access fixes: https://github.com/espocrm/espocrm/releases/tag/10.1.2

### Licensing sources

- https://www.espocrm.com/espocrm-open-source-license/

- https://www.espocrm.com/extension-license-agreement/

- https://www.espocrm.com/features/

### Infrastructure sources

- https://www.espocrm.com/download/

- https://github.com/espocrm/espocrm

- https://www.espocrm.com/blog/espocrm-v10-1-released/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. EspoCRM supports external OpenID Connect providers from version 7.3, with optional user creation and team mapping. Portal OIDC is documented from 7.4. Provider MFA and supported client-authentication methods must be checked separately. Scope: Self-hosted EspoCRM; version-specific OIDC and portal configuration. Source: https://docs.espocrm.com/administration/oidc/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor Docker repository distinguishes a production prebuilt image from development builds and includes database, daemon and websocket configuration. Replace example database credentials and retain persistent volumes. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://github.com/espocrm/docker (reviewed 2026-11-14). Deployment artifact: https://github.com/espocrm/docker. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Sources checked — unresolved. The server guide specifies supported PHP/database versions and recommends a VPS or dedicated server for production. It does not establish a quantitative whole-host CPU/RAM/storage minimum or an HA profile for the proposed workload. Scope: EspoCRM application, database and scheduled/background work; shared-hosting capability is not a capacity guarantee. Source: https://docs.espocrm.com/administration/server-configuration/ (reviewed 2026-11-20).

- License pricing: Documented. EspoCRM core is distributed under AGPLv3. That licence does not include separately sold extensions, hosting or professional support, and it should not be treated as a quote for those services. Scope: Reviewed open-source core; commercial extensions and services are separate. Source: https://www.espocrm.com/espocrm-open-source-license/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed upstream release is 10.1.2, published 2026-11-16. 10.1.2 adds OAuth/2FA and administrator-scope fixes; check the 10.1 database compatibility requirements before upgrading. This is a dated release snapshot, not a support or future-cadence promise. Scope: Upstream espocrm/espocrm release record; commercial editions and deployment packages may differ. Source: https://github.com/espocrm/espocrm/releases/tag/10.1.2 (reviewed 2026-11-16).







## IBM Maximo Application Suite (BYOL)

Customer-managed asset maintenance, work-order and enterprise asset management suite.

- Listing: https://launchinyourcloud.com/directory/ibm-maximo-application-suite/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: ibm
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Kubernetes manifests
- Architecture: Maximo Application Suite on Red Hat OpenShift on IBM Cloud VPC with persistent data services.
- 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.
- Product website: https://github.com/ibm-cloud-docs/maximo-application-suite
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

IBM deployment automation provisions the actual application, not only an OpenShift cluster. Maximo and Red Hat subscription and AppPoints requirements must be agreed separately.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Maximo Application Suite on Red Hat OpenShift on IBM Cloud VPC with persistent data services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-managed asset maintenance, work-order and enterprise asset management suite.

### Deployment boundaries


- ibm: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://cloud.ibm.com/docs/maximo-application-suite?topic=maximo-application-suite-deploying-da (checked 2026-11-19). 


### Cloud deployment evidence

- IBM Cloud Docs (ibm): https://cloud.ibm.com/docs/maximo-application-suite?topic=maximo-application-suite-deploying-da
  Maximo Application Suite on Red Hat OpenShift on IBM Cloud VPC with persistent data services. IBM deployment automation provisions the actual application, not only an OpenShift cluster. Maximo and Red Hat subscription and AppPoints requirements must be agreed separately.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- IBM Cloud Docs: https://cloud.ibm.com/docs/maximo-application-suite?topic=maximo-application-suite-deploying-da

- GitHub deploy.md: https://raw.githubusercontent.com/ibm-cloud-docs/maximo-application-suite/master/deploy.md

- IBM Terms (IPLA): https://www.ibm.com/support/customer/csol/terms/?id=Z125-3301

- GitHub plan.md (License Key Center): https://raw.githubusercontent.com/ibm-cloud-docs/maximo-application-suite/master/plan.md

- IBM Support Licensing: https://www.ibm.com/support/pages/ibm-support-licensing-start-page

- MAS CLI 9.1/9.2 Docs: https://ibm-mas.github.io/cli/

- MAS CLI Releases: https://github.com/ibm-mas/cli/releases

- MAS Ansible Releases: https://github.com/ibm-mas/ansible-devops/releases

### Licensing sources

- https://www.ibm.com/support/customer/csol/terms/?id=Z125-3301

- https://raw.githubusercontent.com/ibm-cloud-docs/maximo-application-suite/master/plan.md

- https://www.ibm.com/support/pages/ibm-support-licensing-start-page

### Infrastructure sources

- https://cloud.ibm.com/docs/maximo-application-suite?topic=maximo-application-suite-deploying-da


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. IBM documents Maximo Application Suite SAML 2.0 federation with external identity providers such as IBM Security Verify, Keycloak, Okta and Microsoft Entra ID. Configure identity mapping and authentication flows for the installed suite release; the article does not establish every newer protocol or provider combination. Scope: Customer-operated Maximo Application Suite SAML integration; not a hosted-service entitlement or blanket protocol limitation. Source: https://developer.ibm.com/articles/single-sign-on-multi-factor-authentication-integration-with-maximo-application-suite/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. IBM documents a catalog deployable architecture through IBM Cloud Projects/Schematics and an official Terraform module. It requires an existing supported OpenShift cluster, entitled registry key and MAS licence file; Core and Core + Manage have different dependencies. Scope: IBM Cloud MAS deployable architecture; version-match the module, suite, database and OpenShift cluster. Source: https://github.com/ibm-cloud-docs/maximo-application-suite/blob/master/deploy.md (reviewed 2026-11-20). Deployment artifact: https://github.com/terraform-ibm-modules/terraform-ibm-mas/tree/24ddaef186771dc4996645c45de84d7ea500933d. Artifact reference: 24ddaef186771dc4996645c45de84d7ea500933d (configuration commit cited by the planning guide; verify suite compatibility). Supporting source: Planning and entitlement prerequisites — https://github.com/ibm-cloud-docs/maximo-application-suite/blob/master/plan.md.

- Minimum footprint / sizing: Sources checked — unresolved. The deployable-architecture guide requires an existing OpenShift cluster and describes 300 GB secondary ephemeral storage per node. That is a storage prerequisite, not a complete suite CPU/RAM/database minimum. Size the selected MAS applications, MongoDB, Db2, storage and HA roles separately. Scope: MAS Core versus Core + Manage on customer OpenShift; selected application and database sizing remains unconfirmed. Source: https://github.com/ibm-cloud-docs/maximo-application-suite/blob/master/plan.md (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: IBM Maximo Application Suite (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.ibm.com/support/customer/csol/terms/?id=Z125-3301 (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Krayin CRM

Self-hosted CRM for leads, contacts, sales pipelines and activity records.

- Listing: https://launchinyourcloud.com/directory/krayin-crm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: Laravel application, database, persistent files and scheduled jobs.
- 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.
- Product website: https://krayincrm.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Hostinger template is a provider package; apply upstream upgrades and configure delivery, TLS and backups separately.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Laravel application, database, persistent files and scheduled jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Self-hosted CRM for leads, contacts, sales pipelines and activity records.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/krayin-crm (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/krayin-crm
  Laravel application, database, persistent files and scheduled jobs. The Hostinger template is a provider package; apply upstream upgrades and configure delivery, TLS and backups separately.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes jitendra-webkul, suraj-webkul, devansh-webkul, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/krayin/laravel-crm/graphs/contributors

- Upstream project: https://github.com/krayin/laravel-crm

### Sources

- Hostinger: https://www.hostinger.com/applications/krayin-crm

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/krayin/laravel-crm/master/LICENSE

- GitHub Releases: https://github.com/krayin/laravel-crm/releases

### Licensing sources

- https://raw.githubusercontent.com/krayin/laravel-crm/master/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/krayin-crm


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed Krayin core documentation establishes application login and roles, but does not establish an external SAML/OIDC provider integration for this self-hosted edition. Laravel authentication or an unverified extension is not sufficient evidence of supported user SSO. Scope: Krayin core; third-party modules and paid customization need their own version-specific evidence. Source: https://github.com/krayin/laravel-crm/blob/master/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Krayin 2.0 documents the webkul/krayin:2.0.1 image and a GitHub Docker/Compose setup. The guide describes persistent application/database volumes. Pin the selected package, replace defaults and configure production networking, backups and TLS; this is not an HA infrastructure template. Scope: Krayin 2.0 Docker installation; image and source versions must match. Source: https://devdocs.krayincrm.com/2.0/introduction/docker.html (reviewed 2026-11-20). Deployment artifact: https://hub.docker.com/r/webkul/krayin. Artifact reference: webkul/krayin:2.0.1.

- Minimum footprint / sizing: Documented. The upstream README specifies at least 3 GB RAM, PHP 8.2+, Composer 2.5+ and MySQL 8.0.32+ with Apache or Nginx. It does not provide a validated 100-user, 1 TB or HA topology. Scope: Reviewed Krayin master requirements; database, storage, backups and redundancy need workload sizing. Source: https://github.com/krayin/laravel-crm/blob/master/README.md (reviewed 2026-11-20).

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Krayin CRM; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/krayin/laravel-crm/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v2.2.8 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Krayin CRM upstream application; verify compatibility with the selected package. Source: https://github.com/krayin/laravel-crm/releases/tag/v2.2.8 (reviewed 2026-11-19).







## Odoo On-Premise

Self-hosted ERP and CRM applications for sales pipelines, business records and operational workflows.

- Listing: https://launchinyourcloud.com/directory/odoo/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Community LGPLv3; Enterprise uses the Odoo Enterprise Edition License; individual add-ons may have other licenses
- Licensing model: open-source
- Installation: Linux packages or source installation with PostgreSQL
- Architecture: Customer-operated Odoo application server and PostgreSQL database
- Operations: Customer or implementation partner hosts the application, secures it, manages backups and applies updates.
- Product website: https://www.odoo.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope this entry to an installation on customer-selected systems rather than Odoo Online or Odoo.sh. Enterprise requires valid subscription entitlements, and the documented registration mechanism periodically contacts Odoo validation services. Do not assume every business app is included in Community.

The listed on-premise offering spans LGPLv3 Community and the separately licensed Enterprise edition. Enterprise and certain app code use restrictive commercial licenses; the fact that some source is accessible does not make all editions LGPL.

Official packages install Odoo as a persistent Linux service and require PostgreSQL. Windows packages are documented for testing/local instances, with production deployment discouraged.


### Category fit

- erp-crm: Modular business applications spanning CRM, sales, accounting, inventory and operations; applications and entitlements vary between Community and Enterprise.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/odoo-crm-erp (checked 2026-11-12). 


### Cloud deployment evidence

- Odoo Community 19 deployment on Railway (railway): https://railway.com/deploy/odoo-crm-erp
  The community template deploys the official odoo:19.0 Community image with PostgreSQL and persistent application storage in a customer Railway project. It does not establish access to Enterprise modules. Review database-version compatibility, administrator credentials, filestore backups and the enabled modules; platform resource charges still apply.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Official packaged installation documentation source: https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise/packages.rst

- Community and Enterprise licenses: https://raw.githubusercontent.com/odoo/documentation/19.0/content/legal/licenses.rst

- Business application scope: https://raw.githubusercontent.com/odoo/odoo/19.0/README.md

- On-premise registration and validation: https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise.rst

- CRM workflow: https://raw.githubusercontent.com/odoo/documentation/19.0/content/applications/sales/crm.rst

### Licensing sources

- https://raw.githubusercontent.com/odoo/documentation/19.0/content/legal/licenses.rst

- https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise/packages.rst

### Infrastructure sources

- https://raw.githubusercontent.com/odoo/documentation/19.0/content/administration/on_premise/packages.rst


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Odoo 19 documents Google account sign-in using the OAuth Authentication module and a configured Google OAuth client. This establishes Google OAuth login; it does not establish arbitrary SAML providers or automatic enterprise user provisioning. Scope: Odoo 19 Google sign-in; configure both the external provider and the Odoo database. Source: https://www.odoo.com/documentation/19.0/applications/general/users/google.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Odoo 19 documentation identifies official Community nightly packages and Community/Enterprise downloads for supported operating systems. Enterprise downloads require a paying on-premise customer or partner account; packages also require PostgreSQL and other dependencies. Scope: Odoo 19 packaged installers; not an IaC template or Odoo Online entitlement. Source: https://www.odoo.com/documentation/19.0/administration/on_premise/packages.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. Odoo 19 provides production worker-sizing guidance: approximately six concurrent users per worker, a CPU rule of (cores × 2) + 1, and RAM estimates for light versus heavy workers. Add cron workers, PostgreSQL, storage and replicas; these are sizing rules, not a fixed 100-user HA minimum. Scope: Odoo 19 Linux multiprocess deployment; named users differ from concurrent users. Source: https://www.odoo.com/documentation/19.0/administration/on_premise/deploy.html (reviewed 2026-11-20).

- License pricing: Documented. Odoo 19 Community is LGPLv3; Enterprise has a separate proprietary licence. The per-user Custom subscription includes the on-premise option. Hosting, implementation, custom-code maintenance and in-app services can add costs; Odoo.sh hosting is excluded from the displayed subscription. Scope: Odoo Community versus Enterprise Custom on-premise; displayed currency and introductory discounts vary. Source: https://www.odoo.com/pricing-plan (reviewed 2026-11-20). Supporting source: Odoo 19 licences — https://www.odoo.com/documentation/19.0/legal/licenses.html.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Oracle E-Business Suite on OCI (Customer-Managed)

Customer-managed Oracle enterprise application suite provisioned or migrated into the customer's OCI tenancy.

- Listing: https://launchinyourcloud.com/directory/oracle-e-business-suite-oci/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Oracle E-Business Suite Suite or Component licenses; separate technology licensing may apply.
- Licensing model: commercial-only
- Installation: Oracle E-Business Suite Cloud Manager One-Click or Advanced Provisioning, or lift-and-shift tooling
- Architecture: Persistent application tier on OCI Compute with database tier on Compute or supported OCI Database services
- Operations: Customer DBAs operate the E-Business Suite environment and OCI resources; Oracle Customer Success Services is optional.
- Product website: https://www.oracle.com/applications/ebusiness/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Oracle describes the OCI deployment as the same E-Business Suite used on premises and applies bring-your-own-license terms. Validate the current certified EBS release, database, region and Cloud Manager combination in My Oracle Support before provisioning.

Oracle E-Business Suite requires commercial Suite or Component licenses; database and other technology entitlements may be separate.

The application tier runs on customer OCI Compute, with the database on Compute or a supported customer OCI Database service.


### Category fit

- erp-crm: Runs Oracle's enterprise financials, supply-chain, human-capital and related business applications in a customer OCI tenancy.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (checked 2026-11-19). 


### Cloud deployment evidence

- Oracle E-Business Suite Cloud Manager in the customer OCI tenancy (oci): https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm
  Oracle documents deploying Cloud Manager inside the customer's OCI tenancy to provision and manage complete E-Business Suite environments on customer OCI resources.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Oracle E-Business Suite Cloud Manager in an OCI tenancy: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm

- Prepare an OCI tenancy for E-Business Suite: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679340.htm

- Oracle E-Business Suite on OCI FAQ: https://docs.oracle.com/cd/E72030_01/infoportal/ebscfaq.html

- Oracle E-Business Suite licensing: https://docs.oracle.com/cd/E26401_01/doc.122/e22950/T422699g54568.htm

- Buyer evidence: iac: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679339.htm

### Licensing sources

- https://docs.oracle.com/cd/E26401_01/doc.122/e22950/T422699g54568.htm

- https://docs.oracle.com/cd/E72030_01/infoportal/ebscfaq.html

### Infrastructure sources

- https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm

- https://docs.oracle.com/cd/E72030_01/infoportal/ebscfaq.html


### Buyer diligence


Research coverage: 12/12 fields (100%); 2 documented, 10 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. The reviewed deployment and licensing sources did not establish a public cloud-marketplace offer that unambiguously entitles the selected self-hosted edition. Obtain the exact offer ID, seller, delivery artifact and edition terms before treating marketplace procurement as available. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Single sign-on: Edition-dependent. Oracle documents EBS SSO through a WebLogic-hosted E-Business Suite Asserter and OCI IAM. Third-party IdPs federate through IAM, not directly with the asserter. Availability requires an eligible IAM domain type (Oracle Apps Premium, Premium or External) or legacy IDCS Standard; user provisioning is separate. Scope: Oracle E-Business Suite Asserter; verify supported EBS/WebLogic/JDK/asserter versions and current identity entitlements. Source: https://docs.oracle.com/en-us/iaas/Content/Identity/ebs/faq_using-ebs-asserter-faq.htm (reviewed 2026-11-20). Supporting source: Legacy IDCS integration component compatibility — https://docs.oracle.com/en/cloud/paas/identity-cloud/uaids/typical-workflow-using-e-business-suite-asserter-authenticate-oracle-e-business-suite-oracle-ident.html.

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Security controls: Sources checked — unresolved. The deployment documentation establishes customer control of infrastructure but does not by itself establish a complete hardened baseline. Review identity, encryption, secrets, network exposure, audit logging, backups, patching and incident response for the selected topology. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Deployment artifact / IaC: Sources checked — unresolved. Oracle documents provisioning through the Cloud Manager Marketplace image, but the public guide leaves the image version/date as a selector and does not establish a fixed image OCID or complete licensed EBS installer manifest. Confirm the exact Cloud Manager image, EBS/application/database bundle and certification matrix through the customer’s Oracle entitlements before deployment. Scope: Exact licensed Oracle EBS/Cloud Manager deployment artifacts; the documented customer-OCI hosting path remains established. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679339.htm (reviewed 2026-11-19).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed sources describe the deployment components but do not provide one complete production sizing model for the buyer's users, data volume, traffic, retention and availability target. Size every application and managed-service dependency. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- License pricing: Edition-dependent. Commercial Oracle E-Business Suite Suite or Component licenses; separate technology licensing may apply. Infrastructure, support and operating labor are separate unless the order states otherwise. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/e22950/T422699g54568.htm (reviewed 2026-11-19).

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).

- Release snapshot / cadence: Sources checked — unresolved. The reviewed documentation establishes a current deployment path but not a durable release snapshot, support window and upgrade cadence for every included component. Record the exact application, installer, image, chart and dependency versions selected for production. Scope: Oracle E-Business Suite on OCI (Customer-Managed): selected customer-operated edition. Source: https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679337.htm (reviewed 2026-11-19).







## Oracle JD Edwards EnterpriseOne (BYOL)

Licensed ERP for financial, supply-chain and business operations in a customer OCI tenancy.

- Listing: https://launchinyourcloud.com/directory/oracle-jd-edwards-enterpriseone/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: JD Edwards application, web and database tiers on customer OCI infrastructure.
- 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.
- Product website: https://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Bring-your-own-licence software and database entitlements are separate from OCI infrastructure billing.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

JD Edwards application, web and database tiers on customer OCI infrastructure. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Licensed ERP for financial, supply-chain and business operations in a customer OCI tenancy.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/ (checked 2026-11-19). 


### Cloud deployment evidence

- OCI JDE Guide (oci): https://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/
  JD Edwards application, web and database tiers on customer OCI infrastructure. Bring-your-own-licence software and database entitlements are separate from OCI infrastructure billing.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- OCI JDE Guide: https://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/

- Oracle Contracts: https://www.oracle.com/corporate/contracts/

- JDE Release 26 Docs: https://docs.oracle.com/en/applications/jd-edwards/

### Licensing sources

- https://www.oracle.com/corporate/contracts/

### Infrastructure sources

- https://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The EnterpriseOne 9.2 Security Administration Guide documents SSO through Oracle Access Management for the EnterpriseOne web client. The integration does not cover Collaborative Portal. OAM deployment, authentication policy and middleware entitlements must be evaluated separately. Scope: JD Edwards EnterpriseOne 9.2 web-client integration; not a native general-purpose OIDC/SAML provider claim. Source: https://docs.oracle.com/en/applications/jd-edwards/administration/9.2.x/eotsc/understanding-jd-edwards-enterpriseone-single-sign-on-through-1.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Oracle documents obtaining One-Click Provisioning archives from Software Delivery Cloud, selecting compatible application/tools releases, accepting the licence, and reassembling/checking the downloaded parts. This is entitled vendor provisioning software, not a public immutable Terraform template. Scope: EnterpriseOne 9.2 Linux One-Click Provisioning; provisioning server, selected release media and licence rights required. Source: https://docs.oracle.com/en/applications/jd-edwards/one-click-provisioning/9.2/eoiol/obtaining-using-archive-files-one-click-provisioning-opl.html (reviewed 2026-11-20). Deployment artifact: https://edelivery.oracle.com/. Artifact reference: EnterpriseOne 9.2; select application/tools release and archive part numbers.

- Minimum footprint / sizing: Sources checked — unresolved. Oracle describes separate provisioning, deployment, development, presentation, application and database roles, including HA/DR architecture choices. The reviewed architecture does not establish a single quantitative resource floor for the selected modules and proposed workload. Scope: Complete customer-operated EnterpriseOne environment; provisioning-server prerequisites alone do not size the application and database tiers. Source: https://docs.oracle.com/en/solutions/learn-architecture-deploy-jd-edwards/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Oracle JD Edwards EnterpriseOne (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.oracle.com/corporate/contracts/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Oracle Siebel CRM (BYOL)

Customer-managed Oracle CRM and enterprise customer-service applications.

- Listing: https://launchinyourcloud.com/directory/oracle-siebel-crm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Kubernetes manifests; Application platform deployment
- Architecture: Siebel application and gateway tiers, database and OCI deployment tooling.
- 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.
- Product website: https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

OCI Cloud Manager and Kubernetes automation are deployment components; their versions do not establish the licensed Siebel application release.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Siebel application and gateway tiers, database and OCI deployment tooling. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-managed Oracle CRM and enterprise customer-service applications.

### Deployment boundaries


- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html (checked 2026-11-19). 


### Cloud deployment evidence

- OCI OKE Guide (oci): https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html
  Siebel application and gateway tiers, database and OCI deployment tooling. OCI Cloud Manager and Kubernetes automation are deployment components; their versions do not establish the licensed Siebel application release.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- OCI OKE Guide: https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html

- OCI Arch: https://docs.oracle.com/en/solutions/learn-architecture-deploy-siebel/understand-oracle-siebel-crm-architecture-oracle-cloud-infrastructure.html

- Oracle Contracts: https://www.oracle.com/corporate/contracts/

- Siebel Bookshelf 26.x: https://docs.oracle.com/en/applications/siebel/

### Licensing sources

- https://www.oracle.com/corporate/contracts/

### Infrastructure sources

- https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Siebel supports integration with external Web SSO: a trusted gateway authenticates the user and passes the subject in a request header. Siebel does not itself provide a SAML assertion consumer/validator. The identity solution and header trust boundary must be designed and supported separately. Scope: Siebel CRM 17, 18 and later as covered by the Security Guide; external authentication is required. Source: https://docs.oracle.com/cd/G30554_01/books/Secur/c-About-Implementing-Federated-Single-SignOn-ak2955398.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Sources checked — unresolved. Oracle documents a Siebel Cloud Manager/GitLab workflow for OKE and database deployment, but the reviewed high-level playbook does not identify a complete version-matched Siebel runtime image/manifest bundle. Confirm the entitled Cloud Manager build, application images and generated deployment payload before production. Scope: Customer-operated Siebel OCI provisioning path established; exact production application artifacts remain unresolved. Source: https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html (reviewed 2026-11-20). Supporting source: GitLab artifact prerequisites — https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/considerations-gitlab.html. Supporting source: OCI resource provisioning — https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/learn-oci-resources.html.

- Minimum footprint / sizing: Sources checked — unresolved. The OCI reference architecture uses three OKE worker nodes plus a separate database, persistent storage and Cloud Manager/GitLab services. It does not establish a complete quantitative CPU/RAM/storage minimum for the proposed Siebel workload or a validated HA capacity profile. Scope: Complete Siebel environment, including provisioning and database services; three worker nodes alone are not a sizing estimate. Source: https://docs.oracle.com/en/solutions/oci-oke-siebel-deploy/index.html (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Oracle Siebel CRM (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://www.oracle.com/corporate/contracts/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## OroCommerce (Community Edition)

Community business-to-business commerce platform with customer and sales records.

- Listing: https://launchinyourcloud.com/directory/orocommerce/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open Software License 3.0 for Community; Enterprise and support entitlements are separate.
- Licensing model: open-source
- Installation: VM image
- Architecture: OroCommerce application VM, database, search and background workers.
- 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.
- Product website: https://www.orocommerce.com/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The vendor AWS image is Community 6.0.2-1; current upstream releases have a different version. The linked AWS guide describes a demo topology, not a production HA sizing guarantee. OSL-3.0 applies to Community; Enterprise is separate.

Open Software License 3.0 for Community; Enterprise and support entitlements are separate.

OroCommerce application VM, database, search and background workers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Community business-to-business commerce platform with customer and sales records.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://aws.amazon.com/marketplace/pp/prodview-m6cl645pcr64s (checked 2026-11-19). 


### Cloud deployment evidence

- AWS Marketplace (aws): https://aws.amazon.com/marketplace/pp/prodview-m6cl645pcr64s
  OroCommerce application VM, database, search and background workers. The vendor AWS image is Community 6.0.2-1; current upstream releases have a different version. The linked AWS guide describes a demo topology, not a production HA sizing guarantee. OSL-3.0 applies to Community; Enterprise is separate.
  Source type: marketplace-offer; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes rgrebenchuk, orocrmdeployer, anyt, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/oroinc/orocommerce-application/graphs/contributors

- Upstream project: https://github.com/oroinc/orocommerce-application

### Sources

- AWS Marketplace: https://aws.amazon.com/marketplace/pp/prodview-m6cl645pcr64s

- Oro AWS Docs: https://doc.oroinc.com/backend/setup/demo-environment/aws/

- GitHub LICENSE (OSL-3.0): https://raw.githubusercontent.com/oroinc/orocommerce-application/master/LICENSE

- GitHub Releases: https://github.com/oroinc/orocommerce-application/releases

### Licensing sources

- https://raw.githubusercontent.com/oroinc/orocommerce-application/master/LICENSE

### Infrastructure sources

- https://aws.amazon.com/marketplace/pp/prodview-m6cl645pcr64s


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. The reviewed AWS offer delivers Amazon Machine Image (AMI) from Oro Inc.. Its package version is 6.0.2-1; verify the contained application and required entitlements separately. Scope: OroCommerce (Community Edition) selected AWS public offer; infrastructure and support charges are separate. Source: https://aws.amazon.com/marketplace/pp/prodview-m6cl645pcr64s (reviewed 2026-11-19). Offer prodview-m6cl645pcr64s: Oro Inc.; Amazon Machine Image (AMI); package 6.0.2-1; https://aws.amazon.com/marketplace/pp/prodview-m6cl645pcr64s.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. OroCommerce 6.0 documents Google single sign-on for back-office users with matching primary email addresses. Enforcing SSO-only login for selected domains is documented from 6.0.7, later than the listed 6.0.2-1 AWS image. Enterprise Microsoft/OIDC features are not attributed to Community. Scope: OroCommerce Community back-office Google login; verify features against the chosen upstream release or provider image. Source: https://doc.oroinc.com/6.0/user/back-office/system/configuration/system/integrations/google-settings/google-single-sign-on/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The OroCommerce 6.0 guide documents the AWS Marketplace VM launch and application-access steps. The guide is explicitly for a demo environment; it is not a production HA template. The listed AWS offer is Community 6.0.2-1 and must be assessed separately from newer upstream packages. Scope: OroCommerce Community AWS demo VM recipe; replace demo data/defaults and design production operations separately. Source: https://doc.oroinc.com/6.0/backend/setup/demo-environment/aws/ (reviewed 2026-11-20). Deployment artifact: https://aws.amazon.com/marketplace/pp/prodview-m6cl645pcr64s. Artifact reference: AWS offer: Community 6.0.2-1.

- Minimum footprint / sizing: Documented. The OroCommerce 6.0 requirements describe a typical single-server baseline of two CPU cores, 2 GB RAM and a fast disk, recommending SSD. Resources depend on data, active users and integrations; this baseline is not sizing for 1 TB, 100 users or an HA deployment. Scope: OroCommerce 6.0 family; provider-image packaging and production workload requirements must be checked separately. Source: https://doc.oroinc.com/6.0/backend/setup/system-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. Open Software License 3.0 for Community; Enterprise and support entitlements are separate. Scope: OroCommerce (Community Edition); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/oroinc/orocommerce-application/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 7.0.4 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: OroCommerce (Community Edition) upstream application; verify compatibility with the selected package. Source: https://github.com/oroinc/orocommerce-application/releases/tag/7.0.4 (reviewed 2026-11-19).







## PaygOps Community Edition

Open-source PAYGO loan, asset-finance, customer and payment operations platform.

- Listing: https://launchinyourcloud.com/directory/paygops/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Application platform deployment; Docker / Compose
- Architecture: PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec.
- 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.
- Product website: https://www.paygops.com/community-edition
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The publisher identifies MasungaTech/PaygOps-Community as the October 2026 Community release and describes GEAPP backing and EnAccess community support. This is a new edition of an established product, not evidence of years of independent Community deployments. Mobile/API, device keys, payments and messaging integrations have their own data and credential boundaries.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- financial-application-management: Open-source PAYGO loan, asset-finance, customer and payment operations platform.

- erp-crm: Open-source PAYGO loan, asset-finance, customer and payment operations platform.

### Deployment boundaries


- digitalocean: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml (checked 2026-11-19). 


### Cloud deployment evidence

- DigitalOcean App Spec (digitalocean): https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml
  PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec. The publisher identifies MasungaTech/PaygOps-Community as the October 2026 Community release and describes GEAPP backing and EnAccess community support. This is a new edition of an established product, not evidence of years of independent Community deployments. Mobile/API, device keys, payments and messaging integrations have their own data and credential boundaries.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The institutional source identifies actual use, public governance or a named community-support program. The linked application source separately establishes installation and licensing.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://www.paygops.com/post/masunga-releases-paygops-community-edition-as-open-source-with-support-from-global-energy-alliance

- Upstream project: https://github.com/MasungaTech/PaygOps-Community

### Sources

- DigitalOcean App Spec: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml

- Deploy README: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/README.md

- AGPL-3.0: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/LICENSE.md

- Commits: https://github.com/MasungaTech/PaygOps-Community/commits/main

### Licensing sources

- https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/LICENSE.md

### Infrastructure sources

- https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The Community documentation describes application authentication and API tokens, but does not establish an external SAML/OIDC identity-provider login path for customer-hosted Community users. Token-based API access alone is not enterprise user SSO. Scope: PaygOps Community user sign-in; commercial or hosted product capabilities are not transferred. Source: https://github.com/MasungaTech/PaygOps-Community/blob/main/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The reviewed source supplies deployment configuration for PaygOps application, PostgreSQL and supporting services through the project DigitalOcean App Platform spec. Set organization-specific secrets, networking, storage and compatible image versions before use. Scope: PaygOps Community Edition deployment example; review the full linked installation instructions. Source: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml (reviewed 2026-11-19). Deployment artifact: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/.do/deploy.template.yaml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The DigitalOcean template allocates two 1-vCPU/2-GB web instances, two API instances of the same size, two 1-vCPU/2-GB workers, and 1-vCPU/1-GB OpenPAYGO and Redis instances. Its three PostgreSQL entries are marked production:false. This is a documented recipe, not an HA or production minimum. Scope: Reviewed Community App Platform template; database capacity, persistent storage and production hardening remain separate. Source: https://github.com/MasungaTech/PaygOps-Community/blob/main/.do/deploy.template.yaml (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: PaygOps Community Edition; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/MasungaTech/PaygOps-Community/main/LICENSE.md (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Relaticle

Self-hosted CRM with configurable customer records, sales pipelines and workflow tools.

- Listing: https://launchinyourcloud.com/directory/relaticle/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: Laravel application, database, persistent storage and queues.
- 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.
- Product website: https://relaticle.com
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

MCP and external AI integrations can disclose or modify CRM data according to the agent credentials; own-account application hosting does not make those integrations private.

GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Laravel application, database, persistent storage and queues. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Self-hosted CRM with configurable customer records, sales pipelines and workflow tools.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/relaticle (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/relaticle
  Laravel application, database, persistent storage and queues. MCP and external AI integrations can disclose or modify CRM data according to the agent credentials; own-account application hosting does not make those integrations private.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes ManukMinasyan, AsmitNepali, Ilyapashayan20, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/Relaticle/Relaticle/graphs/contributors

- Upstream project: https://github.com/Relaticle/Relaticle

### Sources

- Hostinger: https://www.hostinger.com/applications/relaticle

- GitHub LICENSE (AGPL-3.0): https://raw.githubusercontent.com/Relaticle/Relaticle/main/LICENSE

- GitHub Releases: https://github.com/Relaticle/Relaticle/releases

### Licensing sources

- https://raw.githubusercontent.com/Relaticle/Relaticle/main/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/relaticle


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The README documents MCP/API authentication through OAuth 2.1 or personal tokens, but does not establish external SAML/OIDC user sign-in to the CRM. An OAuth authorization server for client integrations is a different login surface from enterprise IdP federation. Scope: Self-hosted Relaticle CRM user login; MCP integration tokens are excluded from the SSO claim. Source: https://github.com/Relaticle/Relaticle/blob/main/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official self-hosting guide provides a Docker Compose deployment with application, queue, scheduler, WebSocket, PostgreSQL and Redis services. Configure secrets, persistent storage, HTTPS, backups and image versions before production. Scope: Self-hosted complete Relaticle stack; multi-container single-host recipe, not HA infrastructure automation. Source: https://relaticle.com/docs/self-hosting (reviewed 2026-11-20). Deployment artifact: https://github.com/Relaticle/relaticle/blob/main/compose.yml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The self-hosting guide lists a minimum of 2 GB RAM, one CPU core and 10 GB disk, recommending 4 GB, two cores and 20 GB or more. These are a single-host baseline for the Compose stack, not validated 100-user, 1 TB or HA sizing. Scope: Reviewed self-hosted Relaticle Compose deployment; storage and replicas must be sized separately. Source: https://relaticle.com/docs/self-hosting (reviewed 2026-11-20).

- License pricing: Documented. GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Relaticle; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/Relaticle/Relaticle/main/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream v3.10.1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Relaticle upstream application; verify compatibility with the selected package. Source: https://github.com/relaticle/relaticle/releases/tag/v3.10.1 (reviewed 2026-11-19).







## SAP Business One (BYOL)

Licensed ERP for financials, purchasing, inventory and customer operations.

- Listing: https://launchinyourcloud.com/directory/sap-business-one/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, gcp, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: Customer-managed SAP Business One application and a certified database on cloud VMs.
- 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.
- Product website: https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Customer-managed SAP Business One application and a certified database on cloud VMs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Licensed ERP for financials, purchasing, inventory and customer operations.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide (checked 2026-11-19). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide (checked 2026-11-19). 


### Cloud deployment evidence

- Azure Docs (azure): https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure
  Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Docs (gcp): https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide
  Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.

- Alibaba Docs (alibaba): https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide
  Customer-managed SAP Business One application and a certified database on cloud VMs. The Azure, Google Cloud and Alibaba guides describe customer infrastructure. Application, database, operating-system and partner entitlements remain separate; check SAP certification for the actual release and topology.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Azure Docs: https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure

- GCP Docs: https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide

- Alibaba Docs: https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide

- GCP SAP B1 BYOL Guide: https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide

- SAP Help Portal: https://help.sap.com/docs/SAP_BUSINESS_ONE

- SAP B1 2026 News: https://news.sap.com/2026/11/sap-business-one-30-years-of-growing-together/

### Licensing sources

- https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide

- https://help.sap.com/docs/SAP_BUSINESS_ONE

### Infrastructure sources

- https://learn.microsoft.com/en-us/azure/sap/workloads/business-one-azure

- https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide

- https://www.alibabacloud.com/help/en/sap-solution/sap-b1-implementation-guide


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. SAP Business One documents external OpenID Connect identity providers registered in the SLD control center, with provider users bound to company users before activation. This is the Business One IAM path, distinct from the separate Cloud Control Center product. Scope: SAP Business One 10.0 IAM documentation; verify the selected feature package, provider and client compatibility. Source: https://help.sap.com/docs/SAP_BUSINESS_ONE_IAM/548d6202b2b6491b824a488cfc447343/13c565324759468490589d60e6c75a92.html (reviewed 2026-11-20). Supporting source: Identity and authentication introduction — https://help.sap.com/docs/SAP_BUSINESS_ONE_IAM/548d6202b2b6491b824a488cfc447343/7f94c5836fad44e6a02322d39e229cc3.html.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Google Cloud guide provisions SAP HANA using its Terraform scale-up guide, then installs licensed SAP Business One using the SAP administrator guide. Infrastructure/HANA automation is not a complete Business One application installer; acquire and version-match SAP media and entitlements separately. Scope: Business One for SAP HANA on Google Cloud; not the SQL Server edition or an end-to-end HA template. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-deployment-guide (reviewed 2026-11-20). Supporting source: Planning and BYOL requirements — https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide.

- Minimum footprint / sizing: Sources checked — unresolved. The provider planning guide requires an SAP-certified HANA machine and workload-specific memory/storage sizing. Its 32-vCPU/834-GB disk performance example is not a universal Business One minimum, and the documented single-node architecture is not an HA design for the proposed workload. Scope: Business One 10.0 for SAP HANA on Google Cloud; CPU, memory, storage and redundancy require a selected certified configuration. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: SAP Business One (BYOL); software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.cloud.google.com/sap/docs/sap-business-one-planning-guide (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SolidInvoice

Customer-operated invoicing, quotations and client billing application.

- Listing: https://launchinyourcloud.com/directory/solidinvoice/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: hostinger
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Docker / Compose
- Architecture: PHP application, database, uploads and scheduled jobs.
- 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.
- Product website: https://www.hostinger.com/applications/solidinvoice
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Scope is invoicing and billing rather than a full enterprise resource planning suite.

MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

PHP application, database, uploads and scheduled jobs. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-operated invoicing, quotations and client billing application.

### Deployment boundaries


- hostinger: Customer VPS account; Customer-operated; control plane: not-assessed. Source: https://www.hostinger.com/applications/solidinvoice (checked 2026-11-19). 


### Cloud deployment evidence

- Hostinger (hostinger): https://www.hostinger.com/applications/solidinvoice
  PHP application, database, uploads and scheduled jobs. Scope is invoicing and billing rather than a full enterprise resource planning suite.
  Source type: provider-guide; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes pierredup, actions-user, claude, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/SolidInvoice/SolidInvoice/graphs/contributors

- Upstream project: https://github.com/SolidInvoice/SolidInvoice

### Sources

- Hostinger: https://www.hostinger.com/applications/solidinvoice

- GitHub LICENSE (MIT): https://raw.githubusercontent.com/SolidInvoice/SolidInvoice/2.3.x/LICENSE

- GitHub Releases: https://github.com/SolidInvoice/SolidInvoice/releases

### Licensing sources

- https://raw.githubusercontent.com/SolidInvoice/SolidInvoice/2.3.x/LICENSE

### Infrastructure sources

- https://www.hostinger.com/applications/solidinvoice


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The SolidInvoice 3.1.3 source documents Google OAuth user login in the shared self-hosted codebase. This establishes Google sign-in, not arbitrary enterprise SAML/OIDC federation. Its separate MCP OAuth server is not evidence of additional user-login providers. Scope: SolidInvoice 3.1.3 self-hosted edition; provider credentials and callback configuration required. Source: https://github.com/SolidInvoice/SolidInvoice/blob/3.1.3/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation guide provides Docker, distribution-package, native-package and Helm options followed by a first-run wizard. The reviewed 3.1.3 source includes a Docker recipe. Choose matching versions and configure durable data, secrets, HTTPS and backups before production. Scope: SolidInvoice 3.x installation paths; application packaging does not establish a complete HA cloud deployment. Source: https://solidinvoice.co/docs/installation-guide/ (reviewed 2026-11-20). Deployment artifact: https://github.com/SolidInvoice/SolidInvoice/blob/3.1.3/docker-compose.yml. Artifact reference: 3.1.3. Supporting source: Docker installation — https://solidinvoice.co/docs/installation-guide/docker/.

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed 3.1.3 README and installation guide specify the PHP/database toolchain and packaging options, but do not establish a quantitative whole-host resource floor for this workload. A PHP memory limit or a small demo container would not establish production HA capacity. Scope: Self-hosted SolidInvoice 3.1.3 application and database; deployment-specific sizing remains to be confirmed. Source: https://github.com/SolidInvoice/SolidInvoice/blob/3.1.3/README.md (reviewed 2026-11-20). Supporting source: System installation — https://solidinvoice.co/docs/installation-guide/system-installation/.

- License pricing: Documented. MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: SolidInvoice; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://raw.githubusercontent.com/SolidInvoice/SolidInvoice/2.3.x/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 3.1.3 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: SolidInvoice upstream application; verify compatibility with the selected package. Source: https://github.com/SolidInvoice/SolidInvoice/releases/tag/3.1.3 (reviewed 2026-11-19).







## Sugar Enterprise On-Site

Customer-operated CRM with a native commercial-contracts module.

- Listing: https://launchinyourcloud.com/directory/sugarcrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Package / binary installer
- Architecture: PHP application servers, persistent uploads, database and search services sized using the vendor's Amazon EC2 guidance.
- 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.
- Product website: https://support.sugarai.com/resources/environments/sugar_on-site_sizing_guide/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

This entry covers licensed Sugar Enterprise On-Site, rather than hosted Sugar products. The AWS guide gives sizing recommendations, not a guaranteed capacity for every integration or a complete operating budget. Contract records, dates and commercial terms do not establish legal drafting or signature parity.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

PHP application servers, persistent uploads, database and search services sized using the vendor's Amazon EC2 guidance. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-operated CRM with a native commercial-contracts module.

- contract-management: Customer-operated CRM with a native commercial-contracts module.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://support.sugarai.com/resources/environments/sugar_on-site_sizing_guide/ (checked 2026-11-19). 


### Cloud deployment evidence

- Sugar On-Site AWS EC2 Sizing (aws): https://support.sugarai.com/resources/environments/sugar_on-site_sizing_guide/
  PHP application servers, persistent uploads, database and search services sized using the vendor's Amazon EC2 guidance. This entry covers licensed Sugar Enterprise On-Site, rather than hosted Sugar products. The AWS guide gives sizing recommendations, not a guaranteed capacity for every integration or a complete operating budget. Contract records, dates and commercial terms do not establish legal drafting or signature parity.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Sugar On-Site AWS EC2 Sizing: https://support.sugarai.com/resources/environments/sugar_on-site_sizing_guide/

- Contracts Module (26.1): https://support.sugarai.com/documentation/sugar_versions/26.1/ent/application_guide/contracts/

- Customer Agreements: https://sugarai.com/legal/customers

- Customer Terms PDF: https://framerusercontent.com/assets/eu2GiGUMAeMAwAn8rqawpURGnP4.pdf

- Sugar Enterprise 26.1.0 Release Notes: https://support.sugarai.com/documentation/sugar_versions/26.1/ent/sugar_26.1.0_release_notes/

### Licensing sources

- https://sugarai.com/legal/customers

- https://framerusercontent.com/assets/eu2GiGUMAeMAwAn8rqawpURGnP4.pdf

### Infrastructure sources

- https://support.sugarai.com/resources/environments/sugar_on-site_sizing_guide/


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. On-site Sugar can use SugarIdentity for external SAML or OpenID Connect sign-in. Activation requires a supported Sugar version, subscription licence key and Sugar Support configuration. SugarIdentity is a vendor-hosted identity service, so this path is not entirely local to the customer account. Scope: Supported licensed on-site Sugar instances; reviewed guide uses Sugar 26.1 and a matching SugarIdentity region. Source: https://support.sugarai.com/documentation/sugaridentity/sugaridentity_activation_guide_for_on-site_instances/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Sugar 26.1 Enterprise guide documents downloading a licensed installation ZIP and running the setup wizard or silent installer on a supported PHP/web/database stack. Downloads require an authorized Sugar account. No public Terraform, Helm or complete cloud template is established by this guide. Scope: Sugar 26.1 Enterprise on-site application installer; provision infrastructure and dependencies separately. Source: https://support.sugarai.com/documentation/sugar_versions/26.1/ent/installation_and_upgrade_guide/ (reviewed 2026-11-20). Deployment artifact: https://account.sugarai.com/downloads. Artifact reference: Sugar 26.1 Enterprise.

- Minimum footprint / sizing: Sources checked — unresolved. Sugar publishes a concurrency-based sizing method, but its numeric reference profiles use legacy EC2 types and Debian 8. They do not establish a current Sugar 26.1 whole-stack minimum or validate the proposed 100-user, 1 TB HA workload. Obtain a current version-specific design before reusing those profiles. Scope: On-site Sugar sizing; historical reference benchmarks are not current supported production configurations. Source: https://support.sugarai.com/resources/environments/sugar_on-site_sizing_guide/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Sugar Enterprise On-Site; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://sugarai.com/legal/customers (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SuiteCRM Self-Hosted

Open-source, customer-operated CRM with marketing campaigns and configurable record workflows.

- Listing: https://launchinyourcloud.com/directory/suitecrm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: railway
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: AGPL-3.0 application; separately selected extensions and services have their own terms
- Licensing model: open-source
- Installation: Official prebuilt SuiteCRM 8 package and server installation guide
- Architecture: Persistent PHP web application, relational database, file storage and background jobs on customer-operated infrastructure.
- Operations: Customer configures and maintains the web/database stack, scheduled and background work, email transport, backups and software security updates.
- Product website: https://suitecrm.com/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Scope is the downloadable self-hosted CRM. Campaigns and workflow configuration are documented, but external email delivery and optional integrations need their own operational arrangements. Confirm compatibility requirements before upgrading; community extensions are separately scoped.

The downloadable application core is GNU AGPL version 3. Paid hosting, implementation and support do not change the listed core license; review any separate extension licenses.

Persistent PHP web application, relational database, file storage and background jobs on customer-operated infrastructure.


### Category fit

- erp-crm: Customer relationship management for accounts, contacts, opportunities, quotes and service processes; this is CRM rather than a complete financial ERP.

- marketing-automation: Targeted email campaigns and configurable workflows around CRM records; campaign delivery requires configured email and background jobs.

### Deployment boundaries


- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/deploy/suitecrm (checked 2026-11-12). Source: https://github.com/gridalpha/suitecrm-railway/blob/main/Dockerfile (checked 2026-11-12). 


### Cloud deployment evidence

- SuiteCRM 8 community deployment on Railway (railway): https://railway.com/deploy/suitecrm
  The community recipe deploys SuiteCRM 8.10 with PHP/Apache, its scheduler and asynchronous worker, plus MariaDB and persistent application storage. The build downloads the upstream SuiteCRM release. Review current versions, initial administrator credentials, mail integration and backups; this does not include separately licensed extensions or vendor-hosted service.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.

- Source for the SuiteCRM Railway image (railway): https://github.com/gridalpha/suitecrm-railway/blob/main/Dockerfile
  The inspected image downloads SuiteCRM-Core v8.10.2 from the upstream release repository and uses PHP 8.3. Confirm the compatibility matrix and update the release and database together when maintaining the deployment.
  Source type: community-template; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The official release notes document SuiteCRM 8.10.2 security and maintenance work released July 31, 2026, and credit community contributors. The vendor case study describes Humanetics Innovative Solutions using SuiteCRM for customer visibility, sales workflows and targeted campaigns; the study does not establish the hosting model of every adopter.

Reviewed 2026-11-10.

- Security maintenance and contributor acknowledgements: https://docs.suitecrm.com/8.x/admin/releases/8.10/

- Named customer implementation: https://suitecrm.com/wp-content/uploads/2025/05/humanetics_casestudy.pdf

### Sources

- SuiteCRM 8 installation: https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/

- Self-hosting and paid service scope: https://suitecrm.com/pricing/

- Marketing campaigns: https://docs.suitecrm.com/8.x/user/marketing-outreach/campaigns-overview/

- Configurable workflows: https://docs.suitecrm.com/admin/administration-panel/workflow/

- Application license: https://raw.githubusercontent.com/SuiteCRM/SuiteCRM-Core/master/LICENSE.txt

- Current security and maintenance releases: https://docs.suitecrm.com/8.x/admin/releases/8.10/

- Humanetics implementation case study: https://suitecrm.com/wp-content/uploads/2025/05/humanetics_casestudy.pdf

### Licensing sources

- https://raw.githubusercontent.com/SuiteCRM/SuiteCRM-Core/master/LICENSE.txt

- https://suitecrm.com/pricing/

### Infrastructure sources

- https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The SuiteCRM 8.7.0+ guide documents SAML configuration and explicitly notes that IdP-initiated logout and POST binding to the logout service are unsupported. Review the stated session-timeout behavior and user mappings. Scope: SuiteCRM 8.7.0+ SAML; logout limitations do not imply login is unsupported. Source: https://docs.suitecrm.com/8.x/admin/configuration/saml/8.7.0-saml-configuration/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The SuiteCRM 8 guide documents downloading the prebuilt application package and completing server installation. Configure the compatible PHP/database stack, permissions and scheduled jobs for the selected release. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/ (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The SuiteCRM 8 installation and compatibility guides establish supported web/PHP/database combinations and recommend the pre-built installation package for production. They do not establish a quantitative whole-stack resource floor or an HA sizing profile. Scope: SuiteCRM 8 application, database and background processing; PHP limits are not whole-host memory requirements. Source: https://docs.suitecrm.com/8.x/admin/compatibility-matrix/ (reviewed 2026-11-20). Supporting source: Production installation package — https://docs.suitecrm.com/8.x/admin/installation-guide/downloading-installing/.

- License pricing: Documented. The vendor states there are no per-user software licence fees for SuiteCRM. Hosting, setup and support are paid services and must be budgeted separately from the open-source software. Scope: Self-hosted SuiteCRM core; managed hosting and optional services are not included. Source: https://suitecrm.com/pricing/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v8.10.2, published 2026-07-31. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream SuiteCRM/SuiteCRM-Core release record; commercial editions and deployment packages may differ. Source: https://github.com/SuiteCRM/SuiteCRM-Core/releases/tag/v8.10.2 (reviewed 2026-11-14).







## SYSPRO Customer-Managed

Customer-managed ERP with sales-contract pricing and stock-item controls.

- Listing: https://launchinyourcloud.com/directory/syspro/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Licensed SYSPRO Installer and application packages on Azure Windows servers
- Architecture: Windows application services and Azure SQL Managed Instance or SQL Server on an Azure VM.
- 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.
- Product website: https://help.syspro.com/syspro-8-2024/topics/sql-managed-instance/sql-managed-instance-ovr.htm
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The Azure server deployment is separate from vendor-operated Syspro Cloud ERP. The vendor's 2026 licensing notice moves customers to named-user subscriptions on regional expiry dates. Confirm the actual contract and current installer before using older SQL Managed Instance recipes; contract-compliance functions do not establish environmental or regulatory certification. The October 2026 module guide describes active customer contracts, allowed stock items and agreed prices in sales orders, quotes and returns; it does not establish legal drafting or a full contract-lifecycle suite.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Windows application services and Azure SQL Managed Instance or SQL Server on an Azure VM. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- erp-crm: Customer-managed ERP with sales, financial and inventory functions.

- contract-management: Contract Compliance Management checks customer contract stock items, dates and prices during sales-order and related transactions; this is a commercial sales-control module, rather than a legal contract-lifecycle suite.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://help.syspro.com/syspro-8-2024/topics/sql-managed-instance/sql-managed-instance-ovr.htm (checked 2026-11-19). 


### Cloud deployment evidence

- Azure SQL Managed Instance (azure): https://help.syspro.com/syspro-8-2024/topics/sql-managed-instance/sql-managed-instance-ovr.htm
  Windows application services and Azure SQL Managed Instance or SQL Server on an Azure VM. The Azure server deployment is separate from vendor-operated Syspro Cloud ERP. The vendor's 2026 licensing notice moves customers to named-user subscriptions on regional expiry dates. Confirm the actual contract and current installer before using older SQL Managed Instance recipes; contract-compliance functions do not establish environmental or regulatory certification.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Azure SQL Managed Instance: https://help.syspro.com/syspro-8-2024/topics/sql-managed-instance/sql-managed-instance-ovr.htm

- Azure SQL MI Guide PDF: https://help.syspro.com/syspro-8-2019-r1/resources/pdfs/syspro-8-sql-managed-instance-reference-guide.pdf

- Contract Compliance Guide PDF (Oct 2026): https://help.syspro.com/syspro-8-2026-r2/resources/pdfs/2026-release/topics/contract-compliance-management.pdf

- SYSPRO Legal & Terms: https://trust.syspro.com/legal/

- Subscription Licensing Notice: https://www.syspro.com/formal-notice-change-to-syspro-licensing/

- Syspro Installer EULA: https://help.syspro.com/syspro-8-installer/i-installation/sys-8-install-installer/sys-8-install-installer.htm

- Updating to 2026 R2 PDF: https://help.syspro.com/syspro-8-2025/resources/pdfs/2026-release/technical/sys-8-updating-to-2026-r2.pdf

### Licensing sources

- https://trust.syspro.com/legal/

- https://www.syspro.com/formal-notice-change-to-syspro-licensing/

- https://help.syspro.com/syspro-8-installer/i-installation/sys-8-install-installer/sys-8-install-installer.htm

### Infrastructure sources

- https://help.syspro.com/syspro-8-2024/topics/sql-managed-instance/sql-managed-instance-ovr.htm


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. SYSPRO documents identity-provider integration with Google, Microsoft and LinkedIn for both Desktop and Web UI (Avanti). Windows/Active Directory SSO is a distinct Desktop path and does not apply to Avanti. Configure the relevant identity-provider and operator settings for the installed release. Scope: SYSPRO 8 2025 identity-provider integration; Desktop and Web UI credentials are configured separately. Source: https://help.syspro.com/syspro-8-2025/g_programs/imp/impssi/impssi.htm (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The SYSPRO Installer installs SYSPRO 8 components and hotfixes using SYSPRO Online Profile credentials and licence-controlled downloads. It manages deployment groups spanning servers, services and clients; it is a vendor installer, not a public cloud IaC template. Scope: SYSPRO 8 installer and entitled software availability; select compatible application and installer releases. Source: https://help.syspro.com/syspro-8-2025/i-installation/sys-8-install-installer/sys-8-install-installer.htm (reviewed 2026-11-20).

- Minimum footprint / sizing: Sources checked — unresolved. The reviewed installer documentation identifies a deployment group containing application servers, services and clients, but does not establish a quantitative CPU/RAM/storage floor for the selected ERP modules and database. A release- and workload-specific sizing design is still needed. Scope: Complete customer-managed SYSPRO deployment, including SQL and optional services; not installer-only prerequisites. Source: https://help.syspro.com/syspro-8-2025/i-installation/sys-8-install-installer/sys-8-install-installer.htm (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: SYSPRO Customer-Managed; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://trust.syspro.com/legal/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






