We now have Starter Projects for Django, Flask, Nest, and Nuxt! What should we build next?

Find & discover services

Share a full catalog of services teams can integrate with so that no one re-invents the wheel

Why create a service catalog?

Don’t let your teams create the same innovations when they should be collaborating

Share services and utilities

Software teams are trained to think about code re-use, but often lack the skills to inform others of their innovations. Service catalogs help engineers publish and distribute their work to others.

Seamlessly extend the work of others

Just because apps and services have been published doesn’t mean others can use them. The best service registries also broker and support integration efforts to ensure code can be extended.

Gain insights into your software assets

Internal engineering utilities are often untracked and undervalued. Service catalogs provide powerful insights into the software components your team has created that provide long-term value to your business.


How to create a service catalog

Search and discovery goes a long way toward improving developer efficiency

Consistent packaging

You can’t expect other teams integrating your app or service to know how to run it. Containerization and a common code registry ensures that everyone uses the same processes for running apps and services.

Dependency management

Cloud applications are more than their containers – they need databases, messaging queues, peer APIs, and more to power critical functionality. Architect includes native network dependency management so that critical resources are captured and resolvable with each deployment.

Search & discovery

A good catalog simply can’t survive without powerful search and discovery. Architect allows your whole team browse through your cloud assets to find services and APIs they can use for new products and features.