IT Landscape Management

Complete transparency and full control
over the custom-built IT landscape: software, tech, people

What is Service360?

Holistic view on the IT Landscape and its maintenance.
360 degree overview of your IT landscape with actionable insights.

Service registry

Catalog of your custom-built services with the insightful metadata: documentation, ownership, APIs, dependencies, releases, SMEs and more

Risk Management

Manage auto-detected business risks imposed on the business by your custom-built applications

Teams

Visualise and control your people cognitive load. Fully automated developer's and team's portfolio.

Big Picture

Explore your services dependencies graph. Find out SPOFs, speed up on-boarding, see how your architecture evolves over time

Tech radar

Document and visualise your organisation's software choices. Provide guidance to engineers on the the solutions

And much more...

Organisation pulse, integrations, DevOps documentation

Enterprise-grade documentation solution

Service360 is built by the team with 10+ years of hands-on experience in the development and maintenance of the enterprise landscapes.

Microservices documentation, team health KPIs, cross-service dependencies management, tech governance, early risk detection — it saves hours of development time and prevents very costly mistakes allowing to concentrate on the business tasks

For the Engineering Manager

One window for platform health assessment with actionable insights: software, tools, people.

  • Teams & Services

    Stay on top of your IT assets. Make sure teams are utilized properly. Keep people engaged and prevent burnouts

  • Risks Management

    Be aware of tech and team-induced risks. Prevent critical failures before they even happen.

  • Tech governance

    Keep the evolution of your organisation tech stack under control. Don't give any chances to a Tech Zoo.

  • Organisation Pulse

    Steer your organisation development with the full transparency over the most important KPIs and health indicators

For the Developer

Comprehensive service documentation in one place

  • Service Registry

    Stay aware of the Services in the landscape. Get maintenance, usage and other information about any service in a couple of clicks.

  • Standardized up-to-date documentation

    Sleep well knowing that your service is properly documented and it will be taken good care of even when you are not there.

  • PostMortems

    Every failure is an important experience and a learning opportunity. Make sure they are not missed.

  • Dependency Map

    Make sure you know your service dependencies and their state. Visualize and explore the landscape

Service360 provides an unprecedented transparency
into the custom-built IT landscape.

Up-to-date DevOps documentation for microservices has never been that easy before!

Very soon

We are working hard with our alpha testers to make sure you will get the best in class product. Subscribe to our newsletter to stay informed about progress and to receive an invitation to our beta test!

Frequently Asked Questions

Short answer: automation and "the secret sauce"

Long one: through the introduction of the DevOps service documentation framework we encourage you to keep documentation:

  1. small: easy to create and maintain
  2. complete: has all the information needed for the service maintenance
  3. uniform: all services share the same structure.
    You can spend your time thinking about business and not on what, where and how you should keep the docs
  4. up-to-date: practice of periodical service audits enforces documentation checks

For the more elaborate answer we encourage you to read the guiding principles we put in the foundation of the Service360.IO

Service360 detects and indicates a lot of service-induced risks like:

  • Low bus-factor
  • Abandoned service
  • Too many risky technologies in one project
  • Missing owner
  • Absent disaster-recovery documentation
  • ... and many more

We encourage you to check a complete list of detected risks in our Risk glossary.

NB: team/people-induced risks are coming soon! Stay tuned!

One of the cornerstones of Service360 - no write interface. All of the information is retrieved from your source code repositories.

Service360 requires read access to your code repositories in order to fetch needed data.

Though one may think that it is somewhat risky, but rest assured that security is our top most priority. We never store or parse the actual service code from your repos. Only handful of documentation files is retrieved and stored on the Service360.io side.

At any given moment you can revoke access.

All access to the data is secured through Auth0, known leader in the identity management, trusted by such companies as Atlassian, AMD, Siemens and many more.

All access to your data is logged and available to you at any given moment in time.

More on that you can read in our setup documentation

PS: In case you have very strict company policy regarding data access - we offer a self-hosted option of Service360!

Yes!

In case you have very strict security policies we offer a self-hosted version of Service360.

Self-hosted option of Service360 is deployed in the AWS account you control.

You are getting billed per each analyzed repository inside of the library. Enjoy complete transparency and predictability of S360 pricing model.

First 5 repositories are completely free of charge.

We are here for you. Do not hesitate to reach us via email or through the website support form.

Still have a question? Ask your question here

Side note: 5% for the Earth

We are strong believers in responsible consumption.
5% of service fees goes to the Earth-supporting non-profit organisation of your choice (plant a tree, save the ocean, etc).
Together we can make a difference!