Yes, all Azure Resources (nearly 1400), are covered by Clophi.

Yes, all the fields that are present in ARM Templates are present in the Clophi.

Yes. Whatever you can do with an ARM template can be done with Clophi, only easier and faster.

Clophi is not just a form for Azure resources; it is a fully dynamic application that corrects your mistakes and alters the available options based on your inputs.

Clophi works in connection with your cloud account and helps you fill any relevant field (such as when you reference an existing Azure resource) related to your own Azure account.

Moreover, Clophi provides a multitude of draft options for every resource, which you can implement with a single click.

Clophi comes with the most detailed documentation both at the general resource level and resource feature level. This documentation is created by Azure experts who have broad experience with Azure resources. This is especially important as the documentation highlights possible pitfalls you may encounter within a certain resource feature, which is not available in the general Azure documentation.

Clophi is fully automated, and the addition of a new resource or a new API version of an existing Azure resource to Clophi happens in a matter of seconds. We keep you updated with Azure

Yes, Clophi allows you to set your secrets as a reference to a secret in a key vault, which you can create in the corresponding secret field. Clophi also gives you the option to set your secrets as plaintext in case you wish to do so.

Yes, it does. For different subscriptions, there are different options available for CI/CD integration.

In these subscriptions, a DevOps project is created for the customer in their Clophi DevOps account. However, it is also possible to integrate your own existing DevOps accounts (Azure DevOps, Jenkins, Github). In this case, the code generated by Clophi (Infrastructure code, Application Code + DevOps Automation code) is pushed into the customer's DevOps account repository, which can then be used by the customer. The customer also has the option to download the generated code or deploy the code via Clophi directly.

The generated code is pushed to a Clophi repository where only the customer has access. The customer can call the code from within their existing CI/CD pipeline via the access rights provided by Clophi. The customer also has the option to download the generated code or deploy the code via Clophi directly.

The customer can download the generated code or deploy the code via Clophi directly.

Whether your deployment is a single resource or a complex infrastructure with multiple resources, Clophi creates the full ARM template as well as the deployment commands in every other language. The generated ARM template is initially pushed to a repository with a cryptic URL. Clophi provides you with this cryptic URL as well as deployment command (in your chosen language). All you have to do is add the deployment command in your program and then run it. Once the deployment command is processed by your program, it will trigger the Azure deployment with the ARM template residing in the repository with the cryptic URL. If you want to modify anything in your deployment, you can easily do this again over Clophi.

If you select an architecture draft from Clophi Architecture Center, which incorporates application code and DevOps automation code in addition to infrastructure code, it provides the infrastructure deployment code in your preferred language as described in the above paragraph. On the other hand, the DevOps automation code, which will implement the application code on the created infrastructure, is provided either as a BASH script or PowerShell script. This depends on the architecture you choose. For example, if you choose an architecture that involves Kubernetes and relevant POD/Services deployments (such as containerized JAVA apps) over this Kubernetes cluster, the DevOps automation code you receive is a BASH script as Kubernetes CLI uses BASH. If you choosean architecture that involves Azure SQL Server, the DevOps automation code that implements the SQL code (such as table creation, stored procedure) on the SQL Server will be in PowerShell as Azure SQL Server is based on Windows MsSQL Server. If you pick an architecture that involves both Linux and Windows based resources, then you will receive both Bash and Powershell scripts. It is also possible that some part of the application code deploys other parts of the application on the infrastructure (e.g. containerized JAVA app running in Azure Kubernetes Services deploying the initial SQL code on Azure SQL Server).

So the steps for this case would be:

1) Deploy the infrastructure with your preferred language via the deployment commands provided to you by Clophi.

2) Deploy the application code on the infrastructure by calling the DevOps automation code (Bash/PowerShell scripts) from your preferred language.

All the Application and DevOps automation codes you receive have adequate documentation which will guide you through each step when you deploy your application within your own CI/CD pipeline.

Not yet.For the moment, we are in public preview, but once we go for purchasable subscriptions, you will be able to request support. However, we are very interested in your feedback, so please do contact us directly if you have any questions and we will endeavour to respond as quickly as we can.

Clophi Enterprise systems have two type of users: 'Clophi User' and 'Clophi Administrator'. You can have as many administrators or users as you like. A Clophi administrator can give access or block a user from using any resource appearing in Clophi. An Administrator can also block a user's access to Clophi's main functionalities such as Clophi, Clophi Architecture Center, Server Configuration Center. Moreover, the administrator can force any resource feature policy on user basis, which gives detailed control of users' capabilities.

Currently, Clophi Configuration Center offers server configuration only for Windows OS with the use of Desired State Configuration framework. After public preview, we will expand Server Configuration Center to include Linux OS.