The OCM Engine is designed primarily to manage [Verifiable Credentials](https://en.wikipedia.org/wiki/Verifiable_credentials) of a given organization as well as DIDComm data exchange. Built as a monorepo utilizing [NestJS](http://nestjs.com) and [Nx](https://nx.dev), it features various applications housed in the `apps` directory and libraries in the `libs` directory. This structure facilitates updates, extensions, and the creation of additional applications and libraries.
The OCM Engine is designed primarily to manage [Verifiable Credentials](https://en.wikipedia.org/wiki/Verifiable_credentials) of a given organization as well as DIDComm data exchange. Built as a monorepo utilizing [NestJS](http://nestjs.com) and [Nx](https://nx.dev), it features various applications housed in the `apps` directory and libraries in the `libs` directory. This structure facilitates updates, extensions, and the creation of additional applications and libraries.
The separation within the OCM Engine allows it to be considered a flexible and extendable framework from both development and consumer perspectives. This modular approach ensures that components can be individually maintained and enhanced, promoting a scalable and adaptable architecture.
The separation within the OCM Engine allows it to be considered a flexible and extendable framework from both development and consumer perspectives. This modular approach ensures that components can be individually maintained and enhanced, promoting a scalable and adaptable architecture.
