Page tree
Skip to end of metadata
Go to start of metadata

Linagora Labs works together whith public and private partners from all over Europe to design bleeding-edge infrastructures solutions.


linagora driven by innovation

The business model of LINAGORA LABS is based on co-innovation through collaborative research: in collaboration with leading universities, partners, and customers, LINAGORA Labs drives the development of promising ideas and prototypes into market-ready open-source software.

LINAGORA Labs gathers many IT PhDs that dedicate themselves to conceive efficient ways to manage evermore complex infrastructures:

  • Large-scale collaboration: ensuring the exchange of information while not bothering user with bloated interfaces or flood of notifications.
  • Robust and flexible infrastructures: facilitate load-balancing, high-availability, automated deployment on heterogeneous environments.
  • Data mining: provide analysts and managers easy way to grasp pertinent information and create tailored reports.
  • Business workflows: how to keep processes as efficient as possible through regular monitoring and refactoring.

Huge commitment for huge ambitions

Born in 2004 and led by Jean-Pierre Lorré, experienced Research Project Manager, our PhD team works with many different partners (Universities, Research laboratories, big IT companies) on French and European projects.

We already achieved more than fifteen projects among which many were middle-ware and infrastructure oriented.
LINAGORA is currently engaged in several French and European projects such as OpenPaaS and gSafe, and more are coming soon.

Open Source spirit, shared knowledge

It is not always acceptable for all partners working on a project to fully publish all results under a free software license. However, we always make every possible effort to convince partners to do so.
As for us, all code source that we produce during the research project realization is published under a free software license.
Some projects led to the birth of exploitable software, such as Petals ESB, ALERT, OpenPaaS (current) or gSafe (current).

Want to learn more? Visit our dedicated platform,, and discover our partners network and rich portfolio!

  • No labels





    Work packages and deliverables

    WP1: Requirements and Architecture

    Leader: PetalsLink

    D1.1.1Requirements of the projectDocument (T0+15)
    D1.2.1Overall Framework ModelDocument (T0+12)
    D1.2.2SocEDA Framework ArchitectureDocumentpending (T0+36)

    WP2: Federated Middleware Layer

    Leader: INRIA/Sophia

    D2.1.1Social Service ModellingDocument (T0+9)
    D2.1.2Social-aware Event Modelling and MatchingDocument (T0+18)
    D2.2.1Esper Engine versus requirementsDocument (T0+18)
    D2.2.2A POC to illustrate Esper engineImplementation (T0+24)
    D2.2.3Identification of requirements to support distributed CEPDocument (T0+18)
    D2.2.4SocEDA distributed CEP engine specification and implementationSpecification and Prototypepending (T0+36)
    D2.3.1Requirements to support reliable and efficient event brokeringDocument (T0+12)
    D2.3.2SocEDA federated middleware specification and implementation V1Document and Prototype (T0+18)
    D2.3.3SocEDA federated middleware specification and implementation V2Document and Prototypepending (T0+36)
    D2.4.1Detailed SOTA of workflow adaptation/flexibilityDocument (T0+9)
    D2.4.2Adaptation Service (AdS) specification according to the workflow engine used in the ESBsDocument (T0+18)
    D2.4.3AdS implementation V1Implementation (T0+24)
    D2.4.4Ads implementation V2Implementationpending (T0+36)

    WP3: Monitoring and Governance

    Leader: Thales Communication

    D3.1.1Specification of the event-based monitoring framework V1Document (T0+15)
    D3.1.2Specification of the event-based monitoring framework V2 and implementation V1Document and Prototype (T0+28)
    D3.1.3Final specification of the event-based monitoring framework and implementationDocument and Prototype  (T0+36)
    D3.2.1Specification of the governance infrastructure v1Document (T0+12)
    D3.2.2Specification of the governance infrastructure v2 and implementation v1Document and Prototype (T0+18)
    D3.2.3Specification of the governance infrastructure v3 and implementation v2Document and Prototypepending (T0+36)
    D3.2.4Web-based administration consoleImplementationpending (T0+36)

    WP4: Design Tool

    Leader: France Telecom

    D4.1.1Relevant SOTA in CEP systemDocument (T0+9)
    D4.1.2Esper CEP interface specification and implementation V1Document and Prototype (T0+12)
    D4.1.3Esper CEP interface specification and implementation V2Document and Prototype (T0+18)
    D4.1.4Extension of the CEP Editor for mashup and eventsDocument and Prototype (T0+36)
    D4.2.1Identification of requirements to support mashup composition toolDocument (T0+6)
    D4.2.2Specification of mashup composition toolDocument (T0+12)
    D4.2.3Web based tool SolutionV0Implementation (T0+18)
    D4.2.4Android UI DesignerDocument (T0+24)
    D4.2.5Web-based tool specification and solution V1Document and Prototype (T0+36)

    WP5: Integration and Validation

    Leader: ActiveEon

    D5.1.1Integrated SocEDA documentation(fr)
    Integrated SocEDA documentation(eng)
    Document and Prototype (T0+18)
    D5.1.2Integrated SocEDA platform and documentation updatedDocument and Prototypepending (T0+36)
    D5.1.3Assessment and delivery of the SocEDA integrated platformDocumentpending (T0+36)
    D5.2.1SocEDA open-source packagePackagingpending (T0+18)
    D5.2.2SocEDA open-source package updatedPackagingpending (T0+36)
    D5.3.1Use case descriptionDocument (T0+9)
    D5.3.2Use case architecture using the SocEDA platformDocument (T0+18)
    D5.3.3Use case prototypePrototypepending (T0+30)
    D5.3.4Use case tuned prototype and reportDocument and Prototypepending (T0+36)
    D5.4.1Use case descriptionDocument (T0+14)
    D5.4.2Use case architecture using the SocEDA platformDocument  (T0+25)
    D5.4.3Use case prototypePrototypepending (T0+30)
    D5.4.4Use case tuned prototype and reportDocument and Prototypepending (T0+36)


  2. Collection of Repositories