cogative

Hello all!
After a period of testing, the Enverido BETA is now over! If you've already registered an Enverido account, you still have access to the the $10/month unlimited subscription plan, even if you haven't subscribed yet. If you haven't registered then all is not lost! As a thanks to the Blesta community for your great feedback and participation in the BETA, here's a coupon code for 25% off for the first 3 months of an Enverido subscription: "THANKSBLESTA". This coupon will expire after Christmas day 2016!
We're also now looking for resellers to help get Enverido to as many customers as possible. We have a Blesta module ready to go that enables you to resell accounts through your existing Blesta installation. If you're interested in this, please drop me a PM!
To summarise, there's now...
Fully functioning Web UI to view and manage licences and products Fully functioning API to create/update/suspend/renew licences Blesta module which supports all of the API's licence functions PHP library which supports all of the API's functions Includes helper classes to simplify licence verification and activation API is fully documented Documentation available for helper classes of the PHP library PHP library code is documented with comments Reseller option available for those who would like to resell Enverido API endpoints are available to integrate this into any platform you currently use Blesta module available PHP library supports all reseller API endpoints Documentation on reseller API endpoints is available In the works...
WHMCS module More detailed reporting and analytics (how many times a licence has been activated, where the activations occurred, etc)  Full online documentation for the PHP library Self-hosted "Enterprise" edition Other features suggested by the Blesta community! Thanks again guys! 

There's no limit to the number of issuing authorities on any of our plans, and we have no plans to introduce one 
Issuing authorities can issue licences for any product, by the way - they're there to make reporting a bit nicer, rather than a technical limitation (IE: there's no one-to-one relation between products and issuing authorities)

See the edit I just made to my previous post, but essentially you could just throw that into your module's root directory, change some of the details to fit your module, add the "enverido/php" line to the "requires" section and you're pretty much good to go .
In the module files themselves (eg: "mymodule.php") make sure to make a "require_once" call to the autoload.php file that's generated by Composer. If you google a general tutorial on Composer I'm sure this'll be covered. But essentially you require_once the autoload.php file, and that file automatically includes all the libraries you installed using Composer. 

Composer will only install from the composer.json in the current working directory, so  as far as I'm aware there shouldn't be any confusion between composer configurations for your modules and Blesta.
I'm not sure if there's a way for Blesta to automatically execute composer to install the module, or if you have to do it yourself manually. I know when I was doing it I just executed "composer install" after uploading the module files. 
Are you trying to use the Enverido PHP library to license your module? 

Merged. Thanks for the pull request.

when i get time i will rewrite my used API for my module that i have used to integrate your system with my licensing digital product .
but i can't promise in the near future as i have to rewrite some other module/plugins than need to be ready when v4 is out .

The GitHub repository deliberately doesn't have a vendor/ directory, so that it can be used with Composer to install the module, and this allows the package to be listed on Packagist. If you want a "pre-packaged" version with a vendor directory already setup, you can download via the marketplace or through enverido itself. 
The reason I ended up doubling up the try/catch statements was that i was finding that adding the if(...) statement underneath each command didn't always trigger the Blesta view with an error, even if the setErrors(..) command had just been executed, and instead the code ended up throwing an exception where certain variables were "null". That's why the try/catches sometimes appear in both files (this and to allow a central "point" to log the API requests, rather than to manually log the request every place it's made in the module.
I'll definitely look into refactoring it in the near-future, but it's a working solution so it's not a top priority right now. Feel free to make a pull request, but by no means feel obligated to - I agree that a cleaner method is certainly a possibility, and I'm going to look into reimplementing the API in the Blesta module, using the PHP library.

Latest Blesta module release (1.3.5) is available on GitHub and the marketplace, now! 
API calls are now logged to Blesta's module logs, and API exceptions are caught and displayed to the user in a nice format. I think I've got them all, but if anybody runs into an exception that isn't caught let me know and I'll push out a new version.
As usual, the update process is a simple drop in the new version, overwriting the old copy.
Let us know if you run into any issues!

I'm just adding catching API exceptions, I'll add logging the request/response to Blesta's module logs at the same time 

I'm just adding catching API exceptions, I'll add logging the request/response to Blesta's module logs at the same time 

the organization if was two word it lead a error in creation via api .
like 'blesta addons' . when i set one work it work perfectly .
and awesmone news is that the DIgital Product Pro Module support licensing now via Enverido.
 

We've just released a new version of the Blesta module, available on the marketplace now!
As @Paul suggested, the module now deletes licences when a service is cancelled, instead of suspending the licence. Suspending the service will still suspend the licence, and unsuspending the service will still unsuspend the licence.
It's a straight-forward upgrade, just replace the current "enverido" folder in Blesta's "components/modules" directory with the new one, then go to Blesta's module administration and click the upgrade button next to enverido!

The PHP library has been updated, licences can now be created and deleted easily using the library. The latest changes are now on GitHub here: https://github.com/enverido/php, and as usual can be pulled into your project via Composer. 
There's no complete documentation for the PHP library yet, but to take a look at how to create and delete a licence via the library in the LicenceTest class, here: https://github.com/enverido/php/blob/master/tests/LicenceTest.php - essentially to create a licence you just need to make an API object using your API key and organisation name. Create a product object using the API object you just made and a product ID, and then create a licence by passing in the values required for the API call (which you can see here: https://docs.cogative.com/pages/viewpage.action?pageId=1409441#id-/licence-POST) - hopefully it's all fairly self explanatory.

Here at Enverido we're happy to announce the first release of our Blesta module!
What is Enverido?
Enverido is a brand-new licensing service which is currently in its BETA testing phase. We hope to make it easier and more affordable than ever before to license your software, and to that end we make available a simple and flexible API, pre-built libraries for a variety of programming languages, as well as a handy web interface to manage and view licence and product information, and finally several "pre-built" integrations for 3rd party services, of which Blesta is the first.
While we believe that Enverido is now at a point where it is ready to begin licensing products, we are aware that it's still in its BETA testing phase! Because of this, we're offering our "business" subscription plan for only $10/month (normally $50/month). This plan allows you to generate an unlimited number of licences for an unlimited number of products. We're also looking for any feedback you have about anything, and we're eager to listen and implement your ideas.
What can it do for me?
We currently have several key features implemented, with others already on the horizon and in development. As it stands, our feature list is as follows:
Create licences for separate products under one account Licences can be locked to a domain name or IP address, or neither Licences can have any duration! Your licences aren't fixed to only being 1 year/month in length! Issue, reissue, suspend and unsuspend licences API documented and ready to use Blesta module ready to use Web UI for manual licence generation, licence management and account management Pre-built libraries for several platforms and languages How does Enverido integrate with Blesta?
Simply create an account on our website (for free!) and install our Blesta module (available on the Blesta marketplace now). Once you've entered your API key and account information into the Blesta module, you'll be ready to go! Simply create a package using the "Enverido" module and you can begin selling licences. Our Blesta module currently has the following features:
Automatic renewal - licences renew automatically when the Blesta service is renewed Automatic suspension - licences are suspended automatically if the Blesta service is suspended Reissue licences - clients can reissue their own licences from within Blesta, either to reinstall their product or to change their domain name, IP address or email Licence management - members of staff can change licence details from the Blesta admin area Instant generation - Licences are generated and displayed in Blesta as soon as invoices are paid Email licence information - You can use Blesta's welcome email to send your customers their licence information via email These features all work in tandem with our own web UI - licences generated by Blesta can still be seen and managed in the web UI if you choose to . 
What does it cost?
Prices for Enverido start from $0. Our homebrew plan is completely free, with no strings attached or requirements to upgrade. To allow as many people as possible to start licensing, we provide plans at a range of price points. Our other two plans are the "Start-up plan" priced at $20/month, and the "Business plan" priced at $50/month. You can see subscription plan information on our website, here.
However, as a thank you for BETA testing our product we're giving you the option to subscribe to a special "BETA testers plan", priced at $10/month - this will allow you to generate an unlimited number of licences for as many products as you want. The best thing? This will be your subscription cost forever, even after the BETA test ends, as long as you stay subscribed! 
How do I get started?
Create a free account at enverido.com Install our Blesta module Take a look at our documentation if you get stuck Like it? Subscribe to the BETA tester plan for only $10/month and receive a great discount! Screenshots
Here are some screenshots of both the web UI and Blesta module to give you an insight into how everything feels. More screenshots of the Blesta module are available on our marketplace listing, and sign-up for a free account to see more of the web UI. 


 
Finally...
Thanks for taking the time to read - we're looking for any feedback or suggestions you might have. Our Blesta module is also completely open-source, feel free to modify as you wish. Have a great day! You can follow development, raise issues and make suggestions here.

@naja7host
Licences can now be removed via the web UI and the API. To remove via the web UI, simply click "Delete" to the right-hand side of the licence where it's listed under the "Licences" page. If you're logged in, click here to get to that page. 
To remove a licence via the API, take a look at our documentation, here. As usual, it's a pretty simple 1-call request that will return either a successful response with some information about the licence you just deleted, or it will return an error and error code if there was a problem (common problems would be that you forgot to add an API key to the request, you're trying to delete a licence that isn't yours, or the licence has already been deleted, or never existed in the first place).
Deleting a licence will be added into the PHP library shortly - If, for some reason, you need it in the next couple of hours, you can make an API request to delete the licence. Just instantiate a new "Api" class and then get the Guzzle HTTP client using the getClient() method. 
The default behaviour of our Blesta module is still to suspend a licence, even if the service is cancelled. We've done this for the sake of data integrity. If you want to change this behaviour, you can fork our Blesta module on GitHub and modify the module to delete a licence if the service is cancelled, instead.
Deleting a licence means that it will no longer be included in your total licence count. An easy rule to remember is that if the licence appears in the list under the "Licences" page, it will be counted as one of your licences - even if it's expired or has been suspended. If there's enough interest, we could add some tools which allow you to delete all the expired licences, or all of the suspended licences, in one fell-swoop, but that's a pretty risky move so I'm somewhat hesitant to add it initially, at least. 
Hope this helps! Let me know if you run into any issues. 

The 10 licences limit includes suspended licences too (this is because these licences can be "unsuspended" and made active again, and it's difficult to predict whether or not your customer is going to decide to renew their licence to unsuspend it - if they did and the suspended licence didn't count towards your totals you could run into problems where an existing customer can't unsuspend a licence they've paid for.
From sometime later today (21st Sept. 2016) you'll also be able to delete licences. both via the API, the PHP library and also the enverido web UI. This will remove the licence and all of its data from the licence server, freeing up one item in your licence count. If you delete a licence, it can't be renewed like a suspended one can, and any products or 3rd party integrations using that licence will stop functioning correctly (eg: if the licence is provisioned in Blesta, and then you delete it via the API from your PC, Blesta will not have a good time). 
We're just carrying out the final tests to make sure everything works properly when deleting licences before we launch it onto the live servers - so like I said, expect it at some point later today. I can drop you a PM when the feature goes live, if you like?

if($licenceValid) { echo("Yay! A valid licence!"); } else { echo("Arrgh! Hide the rum! Ye might be a pirate!"); } LOL
Your code makes me happy.  

Nice platform , maybe when i get time i will integrate API to my digital product module to deliver product with licenses .
 
 
 

Hi,
Sorry for the slightly delayed response. Busy evening!
Thanks for the feedback! We're very flexible on pricing at the moment and I'd love to hear your thoughts if you had any specific ideas on what you would find an acceptable price point. At the moment we picked a few rough figures and went with them and we'd definitely be willing to change these depending on what people are willing to pay. I'm definitely thinking of shifting the pricing down. We've also changed the free tier to include 10 licences, and the start-up plan to include 30 licences (slightly more than before) 
The start-up plan is really there for people testing the waters and/or on a very tight budget for a start-up project - an indy developer if you like. I agree if you are serious about licensing you will want to skip straight to the unlimited tier, but at the same time it doesn't hurt to have the option there. 
ToS and privacy policy are on the way in the next few days, I'll let you know when they are up and accept that you might be unwilling to sign up without them present - they are coming!
API docs are here: https://docs.cogative.com/display/ENVD/API - there's also some end-user documentation and I'm starting to write documentation for the PHP library as I write it. Let me know how you think they could be improved. 
There's been some talk of a licence verification portal type thing - this is something that could be pretty easily achieved with our API using the /lookup endpoint - if a few tweaks are made to the endpoint. Currently you provide a licence shortcode (this is essentially the licence key that the user enters), and you get a product ID and licence ID in return (these are both used to make API requests). With some very simple tweaking it could just as easily work so that if you provided an IP or domain name it returns a licence ID (if there is a licence with that domain/IP) or an error if no licence exists. This could then easily be dressed up with a pretty front-end to act as the portal itself.
I hope this helps! Let me know if you have any other questions and I look forward to your feedback on the API docs and also pricing. We'd love to hear anybody else's thoughts on either of these topics, too. 
Thanks again everybody! 

well I have to tell you that due to liking the idea of paying once and never again unless you need updates I am going to stay with WHMCS licensing addon(and possibly switch to blesta 4.0 license manager plugin if it is better hopefully than 3.x was)
but good luck with your business anyway.

No problem at all!
Sorry if my tone came across as frustrated or irritated, I was just trying to be "to-the-point" and informative in as unbiased a way as possible, just presenting the facts and evidence I could find to support my case. I'm genuinely happy to answer any other questions or concerns you have, if any!
*online hugs* 

Hi Timnboys,
I'll address your points in order.
Most of the pages on the website head to a 404 because I've been working on other products rather than my own company website. I don't get any business through the website at the moment, so it's been left in a bit of a state of "half-doneness" where other projects have taken priority. There's enough there for people to get in touch if they require but not enough to serve as a functional company website. I can understand why that looks odd. 
The domain was registered in 2014 because prior to this I did web development under a different name (Hash Development) - I'm sure you could lookup historical WHOIS records to show there was a domain registered around that time (www.hashdevelopment.com). After this, I did some work under my own name, before moving to the Cogative brand around 2014. Earlier this year I registered as a company in the UK (this is important later).
The WHOIS data listed a Canadian address because contact privacy was enabled. This is a feature available through many domain registrars which allows you to register a domain without listing your residential address. In an effort to put your concerns to rest, I've disabled this and the WHOIS records now list the company's registered office in the UK. You can see this here: https://who.is/whois/cogative.com, you'll also see the enverido domain is registered under the same address: https://who.is/whois/enverido.com
You are correct, the Cogative website is based on Wordpress. This is because there wasn't any benefit to developing a custom CMS for it when Wordpress was readily available to install - this comes back again to the point that there's no business coming through that website at the moment. It's a standard Wordpress install with a Bootstrap 3 theme on top. I can find the base template for you if needed, however I customised the CSS and some layouts to give the site a more unique style. 
Finally, to alleviate any further doubts you can find the UK company registration at Companies House here: https://beta.companieshouse.gov.uk/company/SC524151 - I'm not sure where you're based, but in the UK all companies must be registered through Companies House with correct and up-to-date information. This is done through what's called a "Confirmation statement" which must be submitted once per year. As you can see, the company was officially incorporated on the 13th January 2016 (as I alluded to earlier). The gap between the domain registration and company incorporation was due to the business being "something on the side" until the start of  this year, where it started to play a larger role and it became important to register the company. 
In addition to the genuine company registration, all of our payments are handled through Stripe. The only payment information that we store is the last 4 digits of your card, your card type (eg: VISA, American Express, etc), and a Stripe customer ID. Any actual payment information (full 16 digit card number, expiry date, CVC code, cardholder name) is stored by Stripe. If you take a look at the source of the subscription page in enverido, you can see we use data-stripe attributes on form inputs specifically so that this information never passes through our servers - take a look at Stripe.js (https://stripe.com/docs/stripe.js?) if you want to know more about this. This allows us to be PCI-DSS compliant, and hopefully lets you sit safe in the knowledge that your payment information is stored securely by a recognised vendor. If worst comes to worst, you could even have Stripe refund the full amount of any payment made to enverido. 
I hope this alleviates your concerns. Please let me know any more questions you might have and I'll try my best to clear any misunderstandings up. If this really is a scam, I hope you can see how elaborate it would have to be! Further to this, you are free to try out the homebrew (free) plan without providing any payment information to ensure that enverido really is a functional product.
Once again, I hope this clears up any misunderstanding, but please feel free to ask any other questions. 

No problem at all!
Sorry if my tone came across as frustrated or irritated, I was just trying to be "to-the-point" and informative in as unbiased a way as possible, just presenting the facts and evidence I could find to support my case. I'm genuinely happy to answer any other questions or concerns you have, if any!
*online hugs* 

Take a look at the very first version of our PHP library on GitHub. There are installation instructions on there, too. We'll be implementing more functionality over the next couple of days however licence verification is in there. Tomorrow we'll be tidying it up a bit by using the Verifier class, but it's a start!
We'll start adding updates on our Twitter feed so we don't spam this thread too much.
 

Added as a new feature on JIRA. Feel free to add yourself as a watcher to the issue so you can follow up on developments and add your own input. Thanks