Takipi is Now OverOps

 ● 25th Aug 2016

3 min read

Over the past few months our team has been hard at work on preparing the company to its next stage of evolution.

Over the past few months our team has been hard at work on preparing the company to its next stage of evolution. It has been an exciting journey, and it’s time to switch it into high gear.
Today, we’re excited to announce that Takipi is changing its name, product and brand to OverOps.
In this post, we’ll try to answer any question you might have about this move:

  • What is OverOps?
  • Why change names?
  • What does it mean for the product and the blog?
  • What’s next?

Please feel free to get in touch over email, twitter or use the comments section of this post if you have any additional questions.

What is OverOps?

As OverOps, we’re continuing our mission to liberate developers and operations from searching through incomplete logs for that problematic needle in the haystack. Instead of spending hours searching for answers, teams can automatically identify the root cause of errors, exceptions and defects — speeding software cycles and critical time to market, allowing you to focus on what really matters – delighting your customers.

Why change names?

The company and the Takipi brand were founded back at 2011, and as we saw more users getting onboard – we understood the value of the product for operations and developers alike.
In just one year, OverOps grew by 300%, with new customers like Kaiser Permanente, Samsung, Nielsen, Fox Entertainment Group, HP Enterprise and TripAdvisor.
As mission-critical applications become more complex and real-time, we recognize the need to extend our product offerings to the greater DevOps community.
And besides, people also had a hard time pronouncing and spelling our name so we hope this bit will get easier now 😛

What does it mean for the product and the blog?

The same product you know and love is right there, with a new logo and many new features coming up in the near future. Over the last year, it hasn’t stopped evolving, and will continue to do so. Here’s a quick recap of the features we’ve added during that time:

  • New installation modes: On-prem and hybrid cloud hosting capability for SaaS applications.
  • New Platforms: Docker, Pivotal Cloud Foundry, and Alpine Linux.
  • Trends: The ability to visualize all log events and exceptions in production.
  • Integrations: Sending metrics into more than 20 other tools.
  • Alerts: Proactive alerting notifications for teams, including Slack, HipChat and PagerDuty integrations.
  • Log View: In-memory logging, with INFO levels in production.
  • Dashboard Views: Public and private views.
  • Auto-Archive: Automatically muting all the errors and events we’re not interested in.

OverOps blog, powered by OverOps, will continue to serve the Java community, and publish new research and insights for a growing audience of over 180,000 readers per month.
The experience with OverOps and the connection to the worldwide Java community puts it at a spot between developers and operations. From that point of view, we’re able to share unique content about the current state and future of the industry, and keeping it hands-on.

What’s next?

In the year ahead, apart from new features like better support for user management, the team is planning to expand support to include the .NET CLR (Common Language Runtime). The first non-JVM language that OverOps will support.
Don’t forget to check out our new site: www.overops.com

Have more questions? Please use the comments section below

As a co-founder and CTO, Tal is responsible for overseeing OverOps' product and engineering strategy. Previously, Tal was co-founder and CEO at VisualTao, acquired by Autodesk Inc. (ADSK). Following that, Tal was the Director for the AutoCAD global Cloud and Mobile product line. Plays Jazz drums and Skypes, sometimes simultaneously.

Troubleshooting Apache Spark Applications with OverOps OverOps’ ability to detect precisely why something broke and to see variable state is invaluable in a distributed compute environment.
Troubleshooting Apache Spark Applications with OverOps

Next Article

The Fastest Way to Why.

Eliminate the detective work of searching logs for the Cause of critical issues. Resolve issues in minutes.
Learn More