• What is it ?

      Project made by specialists

      Working in startups since many years, starting from scratch can be tough. In very demanding context, finding a good starting point is major problem. Either technical solution will be long and risky to implement, or third party services will be too limited to achieve your ambitions. We were experts and experienced it in different ways. Now we make something to pass throw this.

      For tech entrepreneurs

      Either if you are a startup or employee(s) in a big company, when you imagine that a technical solution is possible, you will have to make it quick and smart. People expect it to be convinced. Using this tool will bring you a working platform since the beginning that can prove that you were right.

      With tools for DevOps and Architects

      The goal is to make you able to run a business while being a great technical officer. Even if we present our solution as a quick hands-on, you will not be limited when you want to handle deep technical problems.

      Works before costs

      All useful features available since the beginning. We handle a cloud infrastructure where everything is on demand and most of your environments will be deployed in a serverless manner

    • Architecture management innovation

      It's all about how we do it

      Start with a whole system

      Build routes using the build-in framework that has everything working since the beginning

      Develop as usual

      Clone your repositories and run your project with docker

      Optimised CI/CD workflow

      After developing, you can push and instantly deploy every service, daemon, etc

      • Cost efficient : machines are mutualised
      • Scalable : exploitation patterns included via framework
      • Secure : each I/O is well know and best strategy is used

      Third-party orchestration

      Add services "out of the framework", or use official add-on services

    • Framework, READY-to-use

      Simple ops-native framework, with dependencies and connections already set up.

    • Why another framework ?

      Most framework are made to be used everywhere : any stack, any CI/CD environment, any cloud, any protocols, ...

      Well, that makes that your code is not only your business models and rules, but mostly configuration, failover management, protocols conversions, safety guards, and so on. In the end, even for great developers, that is a lot of stress and risk, because there always is something that you haven't done before that you have to do very quickly, and you don't know all side effects you will have to handle (waiting for production bug is not a solution).

      In our case, a new framework is a way to implement safe, robust, and cheap features in a multi-service architecture. All common need are covered. No need to care about side effets. Then when you need to do something "out-of-the-box", you can create your own service in any language that you want (shall only fit inside a container).

      All essential needs instantly, but no limit !

      What can it do ?

      • Authentication
      • Message queues and hooks
      • Cache
      • Advanced notification ("notify a message for this user" is sent to a service that can choose the best way to dispatch, like email/push/web, according to multiple conditions - opt-ins, aggregate, ...)
      • Cross services communication

    • Data-oriented

      After implementing your APIs, you might want to take a deep dive into your data, across all your services

      Use administration tool

      Tools available in development mode to manage your databases with quality : Create, update and deploy your models

      Build your own data lakes

      Easily configure your system to wire all your database into async aggregation data lakes. This way you can setup incredible machine learning models

    • Benefits

      What we get in the end

      Serenity

      All your services are wrapped since the begging, and you can maintain and make it evolve without any pain

      Economy

      Avoid having big teams for administration that don't really improve your business value

      Quality

      Having a system that you can know by heart allows you to make your code very relevant and well tested

      Performance

      The native framework is made to be automatically interpreted and deployed in a serverless manner.

      Cheap, fast & scalable

    • Roadmap

      To achieve this goal, we plan to

      1

      Make a POC

      Enough code to know :

      • How practical architecture management will be
      • How the framework will allow to do as much as others
      • How practical is will be to build pipelines for big data
      • How reusable services can be
      2

      Engage with people

      Set up partnerships and a community of interest

      3

      Release an alpha

      MVP, with development environments only, but operational for side-projects

      4

      Release a beta

      All core features operational :

      • Production environments
      • Development flow
      • Machine learning
      • Teamwork
      • ...and other essential modules
      5

      Get bigger

      Depending on beta feedbacks :

      • Start a development agency
      • Learning paths and certifications for devs and PM
      • More modules
      • Framework in multiple languages
      • Improved processes, UI, UX
      • More events (meetups, conferences, ...)
      • Sport sponsoring (because we like performance)
      Many needs to be defined and done. So a big team to set up !

    • FACTS

      Most Frameworks...

      ...are middleware frameworks. So all the configurations, connections, workflows, environments, dev modes, … shall still be done

      Senior developers...

      ...have much to carry on. Even for a senior talented dev/engineer/whatever, it is hard to provide up-to-date, reliable, multiple-time-tested, secure, maintainable, cost-efficient, understandable-by-other-teammates, quick, scalable system, and so on

    Startuping in Paris with <3