app configuration management, done right

While both Azure App Configuration and smarrtConfig allow you to manage application settings, smarrtConfig offers a broader and more tailored experience — especially for teams that need multi-tenant support, auditability, publishing workflows, and fine-grained access control.

It acts as a central staging area for configuration across multiple applications and environments, giving you full visibility, governance, and traceability — all from a single interface. It also enables seamless alignment with your application infrastructure. For example, a CI/CD pipeline can be notified when configuration changes are published and then update application-specific resources such as Azure App Configuration or Key Vault.

Key benefits include:

• An intuitive management dashboard – no need to grant users access to the Azure Portal

• Fine-grained access control – restrict who can view, edit, promote, or publish values

• Built-in guardrails – enforce naming standards, default values, and require changes to sensitive settings during promotion

• Draft vs Published states – separate staging from live consumption per environment

• Versioning and change history – track who changed what, when, and why

• Tokenisation support – use static tokens (like {env}) to safely manage environment-specific values

• Pipeline integration hooks – notify systems when configuration is published, enabling automated updates to your application environment

No. smarrtConfig is currently delivered as a self-hosted solution, meaning you maintain full control over your infrastructure and data. Once installed, arrt has no access to your environment or configuration data. Everything remains securely within your own Azure tenant.

No, not at the moment but we do have other cloud providers on our roadmap.  At the moment we are just focusing on Microsoft Azure.

smarrtConfig acts as a staging environment for your application configuration. It allows you to import, review, and modify configuration items, then flag them as ready for consumption. From there, configuration can be pushed or pulled—typically via a pipeline—to update your app-aligned configuration in services like Azure App Configuration and KeyVault.

Think of smarrtConfig as the control layer above those services: it gives you versioning, publishing workflows, auditing, access control, and multi-tenant management that Azure’s native tools don’t provide on their own.

Updating App Configuration or KeyVault is usually done via a pipeline, through scripts, or in some cases by giving someone access to the Azure Portal.

But where are those values stored, reviewed or approved before that update happens?

Do you have a simple management tool, with clear visibility and auditability across all your environments?

If the answer is no, then smarrtConfig is the missing piece — giving you a secure, central place to manage, stage, and publish your configuration with full control.