It should be resolved now.

You can choose any hosting you like. https://jsreport.net/on-prem

jsreport is free when you store 5 and fewer templates in the store. The template is typically created using jsreport studio which informs you when you reach the free limit.

You can use jsreport free or commercial in the internal organization without further requirements to disclose something.

The chrome simply doesn't work in the windows azure web app so trying to run jsreport there is pointless.

In case you need to run your app in the windows azure web app, I would recommend to host jsreport outside of your app as a service in a different deployment and use jsreport.Client to connect to it.

Something like this?
https://playground.jsreport.net/w/anon/7r82ZVna

The asset helper is part of the jsreport v3.
Please use the syntax {#asset} mentioned in the current documentation
https://jsreport.net/learn/assets

Thank you for the notice.
Facebook introduced some new requirements for social login. We fulfilled those requirements on Thursday and since then waiting for the Facebook team to recover the login.

Please check this
https://playground.jsreport.net/w/anon/NySKRofa

Can you use folders?

Yes, you can, with "allowLocalFilesAccess:true" in the config. It will create the full path you specify.

Relatedly, is this scalable - are there people actually storing/serving a lot of files using this method?

It should be, let us know if you experience problems.
However, you should consider using a full database instead of the file system for such data volume
https://jsreport.net/learn/template-stores

I have a bunch of legacy PDFs that were created by the system we used before jsreport, but i will still need to have somewhere and serve up for a period. Could i import them in using the odata api maybe or do i just copy the files over into the storage folder and jsreport will automatically pick them up - the documentation is kinda thin on this?

The report consists of Report entity and blob. You can create a Report entity using OData POST and create the respective file representing the blob.

This is how the Report entity looks like

{
      "name": "main",
      "creationDate": "2021-10-16T15:34:48.360Z",
      "modificationDate": "2021-10-16T15:34:48.377Z",
      "shortid": "ZAXTmgE",
      "_id": "mzwMGlnxAFwlICPv",
      "recipe": "docx",
      "fileExtension": "docx",
      "templateShortid": "I2t_EIx7A",
      "contentType": "application/vnd.openxmlformats-officedocument.wordprocessingml.document",
      "public": false,
      "blobName": "folder1/folder2/myfilename.docx",
      "state": "success"
    }

You could POST such json to OData to create Reports, and then create files in blobName path representing the blobs,

In addition or in lieu of the current config file cleanup mechanism, it might be nice to come at it from the other way via the API

Thank you for the idea. I submitted the request to the backlog, you can subscribe here
https://github.com/jsreport/jsreport/issues/825

Is this issue due to jsreport studio reached maximum limits?

No, I see in logs you are in valid trial.

What could be the main reason if template created manually in file explorer or aws s3( Not created from studio) not displayed in jsreport studio?(If id,short id in config file are unique)

This is correct, the jsreport loads data from the s3 during the init. It has no way of knowing you inserted something in the background.

Please try to delete the C:\Users\ThanAs01\AppData\Local\Temp\4\jsreport and try it again.