Thoughts on Moonbase?

[dannytaurus]

I've got a demo call booked with Moonbase on Thursday this week and wondering who in this forum is using them.

If you use them, why do you use them? And if you looked at it and decided not to move, why not?

I'm looking forward to hearing more about how their system works and what advantages it can offer may business.

Context:

• I don't do software licensing and may never do it
• I currently sell only on Gumroad
• I'm a decent Ruby on Rails and, if pushed, JS developer so I'm happy building web applications, backends, etc.

[David Healey]

@dannytaurus I'm just putting the finishing touches on my reworked website using the embedded Moonbase storefront.

My main reasons for switching:

• Tax handling
• Reduced costs
• Less admin work

I'm using a WooCommerce site for displaying products and I've integrated it with the Moonbase embedded storefront using their drop in script. I'm not using the Moonbase WordPress plugin.

I'm also making use of Moonbase's webhooks and API to transfer customer data to my CRM. Although once Moonbase has its own marketing automation system I might not need this.

[Sifres]

@dannytaurus I used moonbase for my licensing and store setup. As a new developer I looked into Hise licensing and MoR around the same time. Moonbase tackles both, is easier to setup then alternatives and requires no synchronisation.

From there I simply tried to implement (Moonbase requires Juce8) and nearly got it. However I ran into a bug. Moonbase response was instantaneous and very helpful. In the end David stepped up and the issue was resolved within a day or two with the Moonbase developer being responsive as well.

Even though I didnt have much alternatives I really like the philosophy of having an integrated system. I met Tobias in Amsterdam and like his view on things and what he tries to accomplish. For instance the mailing integrations have seperate groups from the get go, allowing for trial reminders. Also the system has good API integrations and is very well documented. So right now, for a press release, I wanted to make a bunch of NFR codes. Took about 3 prompts for Claude to figure out the API call with the docs and created a big list. Would have taken hours tbh.

Only thing missing is an MCP

If you want to take a look at the total integration take a look at;
Https://dropout-audio.com/
Hit me up if you want an NFR license so you can see the entire flow.

[HISEnberg]

@Sifres I'm curious then does HISE support Moonbase using JUCE 6? Or do you need to update to JUCE 8? My last memory around this topic is that the JUCE 8 integration into HISE is not fully stable to date.

@David-Healey do you have any content covering Moonbase integration, the advantages it offers, known bugs, etc.?

[David Healey]

@HISEnberg You need to use JUCE8, but it's currently not working, we're waiting for Christoph to fix it. Once it's fixed I've made a PR that makes integrating Moonbase into a HISE project really easy. The PR needs a bit more testing but I'm waiting for the JUCE8 fix first.

I'll be making a video showing how to integrate it once the fix is in place.

[Christoph Hart]

@David-Healey I met with Tobias last week and we discussed improving the integration with Moonbase. I'll be working on a "native" module that integrates with HISE nicely without having to go to JUCE8, but I'm currently swamped with other stuff to do.

[David Healey]

@Christoph-Hart Oh even better

[HISEnberg]

@Christoph-Hart @David-Healey niiiceee thank you for the updates. I'm looking to offer my clients a more consistent solution and Moonbase seems like the cleanest alternative. Glad to hear it is in the works

[dannytaurus]

@David-Healey @Christoph-Hart Is all the talk about JUCE8 and the Moonbase HISE integration related only to licensing?

I don't need to integrate Moonbase into HISE if I'm not using license, right?

[David Healey]

@dannytaurus Yes it only affects the integrated licensing - I'm not using it either.

[Sifres]

@HISEnberg So Moonbase JUCE module requires JUCE8 indeed. Hise isnt stable when being compiled, or when compiling plugins, on JUCE8. So yeah its not working atm. Christoph noted that this is because he did some funky stuff for the MCP integration.

BUT you can work around that by compiling hise on JUCE6, then exporting a plugin. It will fail but it will create a .jucer file and you can pick that up with JUCE8. At least thats my workflow. You could probably script the whole thing. It requires some other steps as well as modifying some Hise source.

TBH if you dont need it right now (as stated, for me it was a neccesary step) I would simply wait for Christoph to integrate it.

@Christoph-Hart great! I feel like it could really benefit the eco system surrounding Hise.