Frequently Asked Questions

  • Can I try GREENSPECTOR?

    Of course! If you are interested in a demonstration or a pilot of our product, do not hesitate to contact us.

  • How is GREENSPECTOR licensed?

    GREENSPECTOR licenses are available for annual rental, with corrective and scalable maintenance included (major and minor versions) as well as user support. We offer different levels of licenses that can be adapted to your context and your number of projects. The unit of account is the number of active projects simultaneously, which means that you can "archive" completed projects at any time to create new projects.

  • Where is GREENSPECTOR installed?

    The GREENSPECTOR suite is composed of: a main server, a source code analysis server, and various plug-ins and probes according to your needs. Plug-ins and probes are installed in your environment: developers workstations, continuous integration platform, etc. For hosting servers, we recommend to retain our offer of "hybrid" installation which presents the best quality-performance-price ratio. In this configuration, the main server of GREENSPECTOR is hosted by us (you benefit from all the flexibility of a "cloud" offer) but the server analyzing source code is installed in your premises (thus the source code of your Software does not go out of your internal network). As an option, we offer a "full cloud" installation or, alternatively, install the solution entirely on your servers ("on premises" offer).

  • Which development languages do you support?

    Software source code analysis is one of the features of GREENSPECTOR. Note that we recommend a broader approach, supported by measuring and steering progress and not restricted to the "static" analysis of the code. That being said, to answer your question, the languages and frameworks currently supported are: - Java, Android - JS, Angular JS, Node JS - HTML, CSS

  • Do you have an "education" price ?

    We are convinced that the learning of eco-design is a must in the training of future computer scientists. That is why we offer higher education institutions educational licenses at significantly reduced prices. If you represent an educational institution, contact us (link to the contact page)

  • What is the difference between GREENSPECTOR and SONARQube?

    SONARQube is a powerful platform for static analysis of source code. The rules repositories are varied and relevant in the field of code quality, security, performance… GREENSPECTOR is a high-performance platform for ecodesign of software. This approach relies in part on static analysis of source code, based on an exclusive repository of carefully selected laboratory-validated rules for the gains they make in terms of energy efficiency. But the approach also relies on the ability to measure the consumption of resources and energy on hardware platforms, for your different cases of functional tests or why not during the load tests. In conclusion, SONARQube and GREENSPECTOR are complementary because they do not pursue the same objectives. The proof: if you already have a SONARQube license, we propose a plug-in allowing to carry out audits of GREENSPECTOR rules via your usual SONARQube.

  • I do performance, I don't need to do eco-design?

    When we do eco-design, we work on the efficiency of the software, that is to say on the optimization of the consumption of resources sufficient to meet the need of the user, and this while maintaining the same performance. When working on performance, we focus on optimizing the response time. The performance approach can in some cases run against efficiency: for example for a website, to quickly display the page one will use several servers (CDN), to carry out treatments at the end of loading of the page… Which will consume a lot of resources. Improving the level of ecodesign at the same time as performance and working on both domains will allow you to go in the same direction: more performance with fewer resources consumed.

  • Do you offer one-time audit services?

    Yes. We are primarily a software publisher, but we carry out audits by supporting the expertise of our experts on the use of our tools. This is often an opportunity to demonstrate that an efficiency approach can resolve concerns that have resisted performance approaches. We can also recommend competent partners who can carry out these audits for you.

  • What is the difference between GREENSPECTOR and the market performance tools?

    They are complementary. Performance tools can be simplified in two areas: resource profiling tools (Profiler JVM for example) and monitoring tools (New Relic, App Dynamics, etc.). GREENSPECTOR is based in some cases on the former, while simplifying the findings and providing the developer with concrete actions. No need to be an expert or master these tools, GREENSPECTOR helps the developer. If further analysis is to be made, the profiling tools can take over from GREENSPECTOR. For the second types of tools (Monitoring), they provide resource consumption information but in a production context and continuously. GREENSPECTOR's approach is to work more upstream (during development) to detect problems of over-consumption as soon as possible. In addition, GREENSPECTOR will work on a more targeted perimeter (such as functional tests), which will allow the developer to identify faster the link between resource consumption and its code, thus being even more efficient in its corrections.

  • Do you have a training offer?

    As a publisher, we support our customers. Any installation of our tool is accompanied by future users training. This training begins with the reminder of the important stakes related to the energy consumption of computing in the context of scarcity of energies that we know. We also offer our customers additional training on the use of a particular module of our tool. If you are a digital services company (ESN, formerly "SSII") do not hesitate to contact us to know more about our partnership program.

  • How much will I gain by optimizing my application?

    That's a good question, thank you for asking. More seriously: like any step of progress, it depends closely on the initial situation, the particular context in which you are, and the efforts you will make to progress. If you are already an eco-design expert, if your team is at the forefront of expertise on the subject, your application will probably be highly optimized and the gains to be expected will be low. On the other hand, if - as is often the case - your application has been developed above all with respect to deadlines, load and functional requirements without any particular efficiency research, then it is likely that the margin for progress will be more important.

  • But still?

    We make no promises about the winnings you can get… But we are proud of the gains we have allowed our customers to get in the past, such as 69% fewer resources on a smartphone, 9% less energy on a native AOSP Android core application (!) or a response time divided by 3 for a business application used by 120,000 employees.

  • What is eco-design software?

    The eco-design of software is an approach which consists in applying the principles of eco-design to the production process of software. It is therefore a global approach aimed at reducing the negative impacts of the software on the environment at all stages of its life cycle: design, manufacture, use, and end of life. Research on Life Cycle Assessment (LCA) of software is still scarce. It is difficult for a non-specialist to know the impacts of a software at each stage according to all the traditional criteria of a stroke (eutrophication, soil acidification, climate change, human health…). However, it is possible to have a simplified approach, in order to estimate the impacts of the production and use phases on the basis of a few, but more easily determinable, criteria (energy consumption, greenhouse gas emissions). In the case of software, it may be instructive to divide the analysis of the phase of use between the "client" part (use by the user, on its machines) and the "servers" part (use by the user, but occurring in a distinct context) to better situate the target of progress efforts. Note that the "network" part also has an impact but that it often escapes the perimeter of influence of the software developer, unlike the "server" and "client" parts. To take a concrete approach, we advocate a pragmatic and common sense approach. We recommend that you begin by studying the relevance of the software - or the new functionality of existing software that you wish to develop. Is the requested functionality useful, indispensable, and optional? What will be its cost of development, but also its cost of maintenance, its impact on the needs of machine resources, on the server side and on the client side? Does it risk premature replacement of hardware? Eco-design begins with a critical analysis of the expected real value. After the decision to produce the software was made, come the general design steps. Particular attention should be paid to the optimization of the technical architecture and functional architecture, to the choice of possible languages and frameworks, in order to meet the "just need" without unnecessarily complicating or over-dimensioning the device planned. Finally comes the development phase itself: the software factory begins to operate. It is in this phase that GREENSPECTOR can particularly help you. Thanks to the functionalities of our tool, your development team can implement the principles of eco-design in order to reduce the impact of the software on the resources of the machines, which ultimately results in energy savings. To do this, the development team must measure the impact of its software (initially, then recurrently to avoid any drift) and work effectively to reduce them, feeding its action plan with expert suggestions of the tool.

  • Is there a label or a standardization of eco-design software?

    « Hé hé hé ». (in Obélix et Compagnie, © Dargaud)

  • What hardware and software are required?

    Call us! Our consultants will provide you with a technical prerequisite document that will answer this question.

  • I have a request about GREENSPECTOR development, how can I contribute?

    If you have ideas of features requests to share, we’ll be pleased to hear them. Feel free to tell us via the contact form.

  • What if I would like to work on GREENSPECTOR?

    If you’re looking for a career, for sure we’re always hiring talented developers. Please, feel free to fill the contact form or take a look at our career offers page!