throbber
6/16/22, 4:08 PM
`
`The Story of Tesonet | We are Tesonet
`
`We’re always looking for bright minds!
`See open positions —>
`
`@) tesonet
`
`Culture
`
`The Story of Tesonet
`
`October 30, 2017 * 2 min read
`
`Ao Tips from the Team
`
`BB-e sola’aoyi
`Tesonet
`
`1 of 4
`
`Tesonetis a place where advanced network security solutions are born. But it hasn’t
`always been this way.In fact, Tesonet as we knowit now cameinto being in 2013.
`
`But what happened before? Wheredid it all start?
`
`The roots of Tesonetare hiding in the labyrinths of IRC channels, where two of the co-
`founders - Tomas Okmanas and Eimantas Sabaliauskas - have met.
`
`Tesonet was founded back in 2008for a single project. And things took over from there.
`
`Try. Fail. Try again. Again and again.
`
`https://tesonet.com/culture/the-story-of-tesonet/
`
`IPR2022-00861, EX. 2046
`
`

`

`6/16/22, 4:08 PM
`
`The Story of Tesonet | We are Tesonet
`
`Since the very beginning, we wantedto work on cutting-edge technology. The Internet
`trends were changingrapidly and it took A LOTof trying and failing before we learned
`whatit takes to succeed in a fast-paced tech environment. Westarted off with online
`
`gaming platforms, we dived into e-commerce,and took up a bundle of other projects.
`Our road had manytwists and turns but working with different technologies gave us
`valuable lessons on both market and technologysides.It took us 35 projects before we
`got where weare now = focusing on networksecurity, business hosting, and big data
`
`solutions.
`
`From 7 to 220
`
`2 of 4
`
`In 2013, the first employees joined the company. Even though our first office was only 17
`square meters big, and there were only 2 of us, we knew thatwefinally were on the right
`track. Not long after, all 7 Teso people went on thefirst workation to Spain. Snowballing
`from there, we were quickly expanding. In 2015, Eimantas and Tomas joined Tesonetfull-
`
`time as all hands on board were needed. We have changed8 offices since then, and with
`550+ people nowit is getting pretty busy.
`
`ORM eweMilely
`
`Asfor the future of Tesonet, we are slowly but confidently stepping onto
`cybersecurityland. Currently, Tesonet is working on various IT solutions as well as
`developing advanced dataintelligence tools. Also, we are working on some pretty
`
`unique business hosting solutions powered by machine learning. There is one thing that
`
`https://tesonet.com/culture/the-story-of-tesonet/
`
`IPR2022-00861, EX. 2046
`
`

`

`remains local capital companyto this day, but we are more than ready take over the tech
`world by storm.
`
`3 of 4
`
`\nS)
`
`Privacy Policy
`
`https://tesonet.com/culture/the-story-of-tesonet/
`
`IPR2022-00861, EX. 2046
`
`6/16/22, 4:08 PM
`
`The Story of Tesonet | We are Tesonet
`
`hasn’t changedsince the very beginning: our global goals and ambitions. Tesonet
`
`Related job positions
`
`Apply for the future opportunities
`
`General ¢ Global
`
`Investment Manager (Mid-=Senior)
`
`General ¢ Vilnius
`
`See others
`
`MCTale
`
`About
`
`Accelerator
`
`Newsroom
`
`Blog
`
`OrTel) g
`
`Contact Us
`
`+370 670 96537
`
`hello@tesonet.com
`
`

`

`6/16/22, 4:08 PM
`
`Cookies
`
`The Story of Tesonet | We are Tesonet
`
`© 2022 Tesonet
`
`Download presskit (10 MB)
`
`@) tesonet
`Tesonetis a proud creator and investor of over 15 various global products and projects.
`
`https://tesonet.com/culture/the-story-oftesonet/
`
`Code200, UAB,et al. v. Bright Data Ltd.
`IPR2022-00861, EX. 2046
`40f4
`
`4/4
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket