Atomic CRM

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

3 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    VM image

  2. Operated by

    Your team

    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.

Deployment boundaries by provider
  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Microsoft Marketplace ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodVM image
InfrastructureServers / containers
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.
Licensing modelOpen Source / Open Core
MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseMIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

7 of 12 fields researched (58%) · 7 documented · 0 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
AvailableEvidence and scope for Marketplace delivery

The official Microsoft catalog identifies this customer-subscription VirtualMachine offer from cloudimg. The publisher package and upstream application have separate maintenance.

Atomic CRM selected Azure public offer · Source ↗ · Offer cloudimg1647283583153.atomic-crm ↗ — cloudimg; Virtual machine · Reviewed 2026-11-19

Documented · Editor reviewed.

Cloud commitment eligibility
Not eligibleEvidence and scope for Cloud commitment eligibility

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.

cloudimg1647283583153.atomic-crm public offer, reviewed 2026-11-19 · Source ↗ · Reviewed 2026-11-19

Explicitly unsupported · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

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.

Atomic CRM with a configured self-hosted Supabase Auth backend; provider-image defaults are not assumed · Source ↗ · Self-hosted Supabase SAML configuration ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

Atomic CRM upstream deployment; Azure publisher packaging has a separate version and operations model · Source ↗ · Deployment artifact ↗ (main (moving branch); match the selected CRM release to its migrations and backend configuration) · Complete self-hosted backend deployment ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

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.

Supabase platform floor supporting Atomic CRM; not a validated CRM or Azure image minimum for 100 users and 1 TB · Source ↗ · CRM backend/frontend deployment boundary ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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

Atomic CRM; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

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.

Atomic CRM upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (5 not researched)
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

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

Community & 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.

Category fit

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

Compare within ERP & CRM

  • Acumatica Private Cloud ERPCustomer-operated ERP with contract billing, renewals and business records.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • Apache OFBizApache enterprise resource planning and commerce application framework.
    • AWS
    Customer-operated · Open Source / Open Core
  • AureusERPCustomer-operated ERP for business, inventory, purchasing and financial records.
    • Azure
    • Hostinger
    Customer-operated · Open Source / Open Core
  • BigcapitalSelf-hosted accounting, invoicing and financial reporting application.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • CelerpSource-available customer-operated business, inventory and ERP application.
    • DigitalOcean
    Customer-operated · Source Available
  • Creatio Customer-ManagedCustomer-managed business application platform with sales, orders and contract records.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • ERPNext Supplier ManagementSelf-hosted supplier records, procurement documents, quotation attachments and supplier scorecards.
    • Railway
    Customer-operated · Open Source / Open Core
  • EspoCRM Self-HostedSelf-hosted CRM with sales records, customer-service features and email campaign management.
    • Railway
    Customer-operated · Open Source / Open Core

Showing 8 of 22 other listings in ERP & CRM. These products address related workflows; read their category-fit notes before comparing scope. See all of ERP & CRM →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Microsoft Marketplace ↗ · Azure

      Marketplace offer · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory