Purchasing Extensions for Self-Hosted EspoCRM (Docker VPS)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tomasrotek
    Junior Member
    • Sep 2024
    • 4

    Purchasing Extensions for Self-Hosted EspoCRM (Docker VPS)

    Hi everyone,

    We’ve deployed EspoCRM on our own VPS using Docker and are actively building on top of it. We’re now looking to enhance its functionality with some official extensions, starting with the Google Integration extension.

    However, we’re unsure if EspoCRM extensions are available for purchase and use on self-hosted instances or if they are restricted to customers using EspoCRM’s cloud service.

    Can we buy and install extensions on our on-premise deployment? If so, are there any specific licensing terms or installation requirements we should be aware of?

    Thanks in advance for any insights!
  • macistda
    Member
    • Jul 2022
    • 86

    #2
    We use EspoCRM on premise (VM, not Docker but should be the same) and use the following official extensions: Advanced Pack, Sales Pack, Outlook Integration. If you want to test, you can request a personal demo (https://www.espocrm.com/personal-demo-request/) Do you have SSH access to your VPS?
    Hint: I am not an Espo employee or reseller, I am a customer like you.

    Comment

    • yuri
      Member
      • Mar 2014
      • 8695

      #3
      Hi Tomas,

      EspoCRM extensions are sold primarily for on-premise. The cloud plans already include extension.
      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

      Comment


      • tomasrotek
        tomasrotek commented
        Editing a comment
        Hi, thanks for the response. It’s great to know that extensions are available for on-premise installations.

        I have a follow-up question about how the extensions are structured technologically. We tested the Real Estate extension and noticed that it provides source code, allowing us to adjust its logic and build on top of it. Is this approach consistent across all extensions? We’re considering using an extension as a starting point for further development in our system and need the flexibility to extend its logic.

        Additionally, we’re curious about the licensing terms. Since the purchase page mentions a license, we wonder why it isn’t just a one-time payment—perhaps it’s related to providing ongoing upgrades?

        Thanks again for your insights!
    Working...