1

How commercialize a template ?

Since several days, I'm working on a ninox template, I would like to "market" it through a license system. To describe how it works: everyone can pay to use my template for a specific period (1 year for example). Then, the rights are withdrawn once its license is completed in case of non renewal. Is it possible to create this in ninox? Maybe through third-party applications with Zappier?

18replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • I'm also interested in this issue.

    Like
  • I'm also interested in this issue.

    Like
    • Maxime
    • Maxime
    • 3 yrs ago
    • Reported - view

    Someone can help us ?

    Like
  • Hi all, 

    Thank you for your interest in developing Ninox templates. 

    Could you please send us an E-Mail to support@ninoxdb.de in order to talk with us about our partner program?

    We are looking forward to get in contact with you. 

    Thank you very much.

    Best, Jörg

    Like
  • I have made my database (still in construction and far of completed - due to the limited time i can spend on it) with a licence field and calculated depending on the Owners Company's VAT NR to unlock the full features. Once registered (the customer send me an email with his VAT number to get his licence)a hidden yes/no field is triggered and with that field some other fields are active(writable) or not or even hidden. This though is not period specific but you can implement that somehow. 

    Like
  • I've done something similar - but the code is based on a date in the app. The process is:

    1. the user goes over existing licence limit (number of records) and is prompted to visit a webpage to upgrade

    2. user completes Cognito form, including making payment by PayPal

    3. Integromat takes the form value and looks up the appropriate licence key (which level and what date) from a database (not in Ninox at the moment but will be when Integromat supports Ninox natively)

    4. Integromat emails the licence key to the customer and updates database to show licensee information.

     

    This all works - but the biggest issue with supplying Ninox apps is how to manage updates - there is no mechanism available to update copies of the app in use by your clients. This means you will realistically be limited to supplying apps as just templates - i.e. to be used as-is - unless you intend to provide a manual update process for customers.

    Like
    • Maxime
    • Maxime
    • 3 yrs ago
    • Reported - view

    Thanks for your answers everyone,

    Julian, you system is very interesting, but I have some questions about that.

      "1. the user goes over existing licence limit (number of records) and is prompted to visit a webpage  
      to upgrade"

    How limit the number of records in Ninox for a user?

      "4. Integromat emails the licence key to the customer and updates database to show licensee                  
      information."

    Once the customer buy the licence key, How to tell Ninox to unlock the record limit for this user?

    Thanks. 

    Like
  • Hi Maxime

    You're right of course, thhat it isn't possible to actually stop a user adding records over the licence limit. So what I do is have a Trigger on create which sets an flag called Editable if the record is over the number:

     

    let licences := first(select 'System Settings').'Licenced Contacts';
    let contacts := count(select Contacts);
    if contacts > licences then Editable := false end

     

    If this is the case, all of the fields on the form dissapear (their Display option is set to 'Editable') and instead I display some text and a button which deletes the useless record and takes them to System Settings (a table) where they can see a link to the upgrade form (a Cognito form) which takes their payment and then Integromat does it's thing.

     

    Not all that elegant but the best I've been able to come up with so far - it would be nice to have control over whether records could be added through code...

    Like
    • Katie Rayner
    • Be Legal Property Compliance
    • Katie_Rayner
    • 2 yrs ago
    • Reported - view

    I would like to commercialise a template also (a database I have been working on for months) - and market it to people in a similar industry to my own.  Would it be possible for us to charge a once off fee and then we email the user a copy of the template with a link to Ninox?  Then they just pay Ninox their monthly fee.

    All the coding to make it a licensed agreement sounds too hard for me personally (although it would probably make more money that way).

    There could be various levels of the template, so just a basic one, and then a more advanced one, etc, so they can choose which template they want to spend the money on.

    Like
  • Hi Katie

    Of course what you suggest is possible - the only possible issue is that your customers could share your template with others without paying you for it. Whether this is likely to be an issue I can't say of course.

    It may be worth contacting Ninox about their Partner Sceme as you may be able to earn some additional money through an affilliate link.

    Like
  • I would be interested in a feature that allows developers to sell usage of their app as well.  I've seen other low code systems that allow a developer to add separate "user accounts" into an online application.  Some sort of version control would be helpful too, in order to facilitiate upgrades for all customers at the appropriate time. (Wish list item, of course).

    Like
    • MODA
    • MODA
    • 1 yr ago
    • Reported - view

    Gitnox https://gitnox.com can help you in this. We“re already using it to sell and scale our own apps

    Like
  • Hello everybody. Gitnox is very interesting thing, but i have a dout about that you have to enter your private information: user name and password and allow access to all your datebases linked to this account even to your code🤔. My apple account notified me about leaked user name and password. Is that normal? Paranoia?

    Like
    • Sean
    • Sean
    • 1 yr ago
    • Reported - view

    I think it“s wise to be cautious. A search for Gitnox on the German language forum returned no results 

    Like
      • MODA
      • MODA
      • 1 mth ago
      • Reported - view

      Hi everyone, sorry i just saw your replies. Old forum UI was not friendly and i never saw your answers.

      Sean you're absolutely right when it comes to providing those credentials. We've implemented every possible security best practice to protect that call on our side, nevertheless, you're still providing those creds at some point.

      One simple way to go around this is to use a separate account which would be enabled before the gitnox call, then disabled (around 2 seconds).

      Another solution is to use our gitnox CLI module. It's a bit more tedious, but works very well for our clients who had this constraint. In this scenario, credentials will never leave your network and you will be performing the updates through the CLI.

      Gitnox will allow you solve several problems.

      • Having a DEV, Qualification & a production environment for your clients. Works like a charm, especially with the newly released Gitnox Control Center App.
      • Creating a master app, and deploying several thousand encrypted copies of it to your clients and charging your clients the use of that app (ex: our app trobia.fr)
      • In more advanced scenarios, gitnox allows you to scale your databases horizontally & quite infinitely. The ninox platform is very optimized and efficient in the way it manages the database, but when it comes to handling 150 million records, better find a way to split that database into multiple pieces (all gitnoxified) and handle records 15 million at a time. Of course you could scale vertically by asking for more ressources on your ninox instance but sooner or later you're gonna hit a wall. Ninox already out performs very well in handling those records, but it's a conceptual / design issue that you'd need to handle somehow for very (very) large deployments.
      • 🔥 Upcoming : the ability to inject an app inside another app, what is commonly referred to as plugin. Probably the would be some sort of a store out there, controled by ninox where you get certified plugins that you can buy & inject  into your app (we kinda already do it through the gitnoxify button inside gitnox)
      • 🔥 Upcoming : i18n, downloading the french version or your app, or the german version of the same app (or whichever language?)....that's also on the roadmap, we're waiting for our first client who'd ask for it to implement it.

      Hope all that helps & sorry for not being reactive. Hope new forum will notify me back your replies

      Best !

      Like
    • support
    • support.2
    • 1 yr ago
    • Reported - view

    Hi everyone, you“re definitely right regarding your questions. Better discuss this over the next partner call as these questions were already raised. I presented already our work in one of the calls in August, will be glad to re-present it. Could you ping me on slack. M.Daaboul 

    Like
  • Please explain how to ping you on slack. I never use this app. 

    Like
  • Join me on Slack -- it’s a faster, simpler way to work. Sign up here, from any device:

    https://join.slack.com/t/uralbuild/shared_invite/zt-jxw8vwub-QYkylD_t5F43sQfiRaObvw

    Like
Like1 Follow
  • 1 Likes
  • 1 mth agoLast active
  • 18Replies
  • 4020Views
  • 1 Following