Freeway® NEMO is available in 3 different editions:

Express Edition	It's FREE and downloadable directly from Downloads or snowcovered catalog. Allows for the creation of simple consultation portals  with a license limitation of 1 http alias activated (besides test/development localhost) to be requested directly via email (see “License Agreement”).  This edition is only available as 1.1 version. Please read Edition Comparition section to see its limitation.
Standard Edition	Is the most complete edition that offers all the functions of the package with a licensing policy based on the http-alias of the portals for which the product will be activated.  Includes appropriate documentation, periodic fixes and technical support through the product  forum and snowcovered helpdesk based on the licensing conditions. Buy It Now !
Developer Editon	Its contains all Standard Edition features and a set of modules designed for .NET Developers; this edition allows for the creation of enterprise application portals, exploiting the maximum extensibility of the product. With this edition you can also use Nemo SDK library to develop your own Nemo-powered DNN modules. Buy It Now !

Contracts based on more extensive licensing policies are available; for information or clarifications, send your specific request to the following address: nemo@eurosystem.it

Freeway® NEMO are composed of 7 integratable and combinable modules:

• Nemo.Console: allows for the administration of the datasources from which to extrapolate data and context variables according to their purpose: DNN, Portal, User, Session, Local, Preferences);
• Nemo.Filter: allows for the design of a panel composed of arbitrary parameters based on which the user can specify search criteria that influence and guide the data query.
• Nemo.DataViewer: allows for the design of data presentation layout extracted in tabular or single record form.
•  Nemo.TextHtml: this is the Nemo variant of the DNN TextHtml core module. Allows for the use of Nemo context variable into html text.
•  Nemo.CommandBar: It allows to specify a bunch of Nemo-command objects which can be used via javascript to carry out Reload\Show\Hide operations on any Nemo module present in the page.
•  Nemo.Container: It is a module designed specifically for ASP.NET developers; it allows to load dynamically any ASP.NET User Control and at the same time giving it AJAX features.
  Following the specified naming convention it’s possible to supply the User Control with a set of public properties which can be used to customize its behavior inside the page where is placed (e.g. use the same Nemo datasource configured in the portal, read some specific property, etc). The development of the UC doesn’t require any Freeway Nemo or DNN library but can benefit, if necessary, of the Database Helper Classes present in the Nemo SDK.
•  Nemo.ScriptCenter: It is another module designed for developers. It allows the definition of a Javascript functions library which can be called from other Nemo modules.

The following is a description of the common characteristics offered:

• Each module request, on the same page or on different pages, can dialogue with the others in a completely AJAX action
• Communication between modules occurs on the basis of the promotion of context variables that are veritable programme variables (strong typed)
• The context variables are intended for the following purposes: DNN,  Portal,  User,  Session,  Local,  Preference,QueryString, ROW.
• The context variable, through a specific placeholder-based syntax ({.< variablename>}) can be utilized to promote or dynamically compose other properties of the modules or to construct them where conditions of the SQL query and data extraction. 
• Formatting of data compatible with the culture of the user profile.
• Highly personalizable formatting of data on the basis of the String.format stynax of .NET Framework coordinated with the direct use of the tag HTML.
• Logging (with a configurable level of detail) of all queries and operations conducted by the modules; indispensable portal debugging.
• Tested on Microsoft SQL Server and Oracle™ databases, but useable on any DBMS for which there exists an Ole DB Provider or ODBC Provider.