Your modern microservices catalog is here
Easily keep track of your growing landscape of services.
Never lose track of service ownership
Unowned services cause unnecessary pain. Track the team that owns each service and keep it up-to-date across the changing organizational landscape. Know that all of your microservices are being well-developed, operated and maintained.
Onboard engineers faster
Information about a team's services, whether its documentation, dashboards, and bug trackers -- you name it, tends to exist in multiple tools. effx creates the single pane of glass to help them know the ins-and-outs of their team's resources.
ChatOps with Slack
Pull up critical information about services directly where your conversations are happening -- in Slack.
Jump to all of the key dashboards, channels, or tools in conversations or on the go.
We provide various integrations to get your service data into effx. The primary method is via a YAML file you can drop within your Git repository. We have integrations with most Git providers to automatically lint and sync the information into effx when you push to your main (or master) branch.
Within our platform, you'll find our YAML builder where you can construct your YAML files using a helpful wizard and view changes to the YAML file in real-time before you commit to your code repository.
For more information on our Git integrations, our effx-cli tool, and more, check out https://effx.com/help
Yes it is!
Our platform provides value for teams from 2 services to thousands. If you've started your journey to microservices, or a service-oriented architecture, our features can enable you to build operationally sound infrastructure from the start.
Currently effx only runs in a Software-as-a-Service environment. If you're interested in a more flexible deployment model, we'd love to chat with you about your requirements.
As for data, effx can work in various ways. We can pull from integrations that you give us access to (these are typically 3rd party hosted products or popular open source tools) but also from a push mechanism where you only send the data to us that you want. This gives you firm control over the data in effx.
Service dependencies can be defined in effx in two ways:
- Integrations: we support most popular service mesh setups to automatically ingest and display your service dependencies
- Via static configuration: we allow for dependencies to be defined within your YAML configuration.
We offer a full REST API for retrieving (and writing) data to effx.
You can find our API documentation here.
Ready to get started?
