support for your release pipeline

We understand that a software development lifecycle requires an application to be deployed and...

deployment tooling

DevOps, automated build and automated release are important to us in maintaining our quality and...

security permissions

cloco currently supports a role based access model offering administrator and user roles with read...

client-side encryption

Configuration objects are securely stored by cloco, but since we provide cloco as a service we...

version history

Depending on the subscription level, cloco will record a version history and retain the most recent...

Sign up for the latest cloco articles and updates! Don't worry, we'll never share your email address.

Name

support for your release pipeline

We understand that a software development lifecycle requires an application to be deployed and tested in a number of different environments and that each of these environments will require different configuration settings for URLs, performance related settings, connection strings to name but a few.  When you save a configuration object in cloco you specify the environment associated with the object.  When you incorporate the Client API into your application you also set the environment to use,...
Continue reading

deployment tooling

DevOps, automated build and automated release are important to us in maintaining our quality and agility.  We want you to have the same experience as well and because of this we ship deployment tooling with the cloco Client API.  This can then be incorporated into your deployment framework of choice. The cloco CLI tool can be used to manage cloco and your configuration objects remotely from a command line.
Continue reading

security permissions

cloco currently supports a role based access model offering administrator and user roles with read and read-write access scopes, meaning that different authenticated users will have different privileges. Permissions are assigned within a subscription and application at an environment level.  For example, this allows application services to have read access to configuration objects within an environment and administrative users to have read-write permissions to manage and update the same...
Continue reading

client-side encryption

Configuration objects are securely stored by cloco, but since we provide cloco as a service we wanted customers to be safe in the knowledge that their configuration data is protected when it is not on their premises.  It is for this reason that we incorporated encryption functionality into the cloco client API.  This means that whenever configuration data is stored in the cloco service, you can be confident that the data is encrypted and not accessible by anyone other than yourself.
Continue reading

version history

Depending on the subscription level, cloco will record a version history and retain the most recent versions of each configuration object.  This allows you to audit changes to ensure that unauthorized changes have not been made, and to assist in fault finding when version updates are made.  A known good state version is supported for an environment to allow all of the configuration objects within that environment to be tagged with that version independent of the version number of each...
Continue reading

client-side validation

Sometimes you want to ensure that your configuration is valid before it is saved to cloco so that your applications do not have to handle broken configuration.  Because cloco treats the configuration object as opaque when stored in the service, the validation must be performed client side in the cloco Client API.  Out of the box, JSON and XML configuration objects are supported with the option to provide your own custom validation logic.
Continue reading

client-side caching

In order to improve performance, the cloco Client API will keep a cached copy of each configuration object retrieved, so that access to configuration is quick and from memory almost all of the time. In micro-service architectures the cloco Client API may be hosted in its own micro-service providing configuration to all of the other services running on the cluster, thus ensuring all configuration objects for the environment are not cached per micro-service.  This avoids an undesirable...
Continue reading

client API for Node.js applications

We recognize that not everyone wants to use cloco by accessing the REST API directly and would prefer to use a client API using a language and framework familiar to them.  Our current release will support Node.js applications, but the plan is to provide client API’s for many of the more popular languages such as PHP, C#, Java, Go, Python and frameworks such as .NET Core, Angular, Knockout, Express, Docker and so on. Your feedback will directly determine our roadmap.
Continue reading

any configuration format

Using the cloco client API you can store any type of object in any format that you choose.  The cloco service will tag the configuration object with metadata in order to manage it but does not inspect or alter your actual content, so you are not restricted as to the type or structure of configuration data you need to save. If you do use recognized formats such as JSON, XML or yaml, cloco provides structural validation to give you an extra safety measure that all is well with your data...
Continue reading

rollback of deployed configuration

Built as part of the version history feature, we also support rollback to a previous stored version at both the level of the configuration object as well as rollback to the last known good state for an environment.  In our experience it is essential that a faulty deployment can be backed out quickly and all you have to do to roll back is to tell cloco which previous version you wish to promote back to being the current version.
Continue reading

want to try cloco for yourself?

click here to sign-up for our early beta program

Let's get started!

questions?

we are here to help.

get in touch