Episode 36: ActiveState – Open Source Languages Platform with Bart Copeland

Bart Copeland, is the CEO of ActiveState. Since the 90s, millions of developers have used the famous ActiveState distributions of Python, Perl and Tcl. In this episode, Bart narrates ActiveState’s journey, including several pivots and ownership changes. Stay tuned to the end to find out how they were able to pivot to the open source...

The post Episode 36: ActiveState – Open Source Languages Platform with Bart Copeland first appeared on Open Source Underdogs.

Bart Copeland, is the CEO of ActiveState. Since the 90s, millions of developers have used the famous ActiveState distributions of Python, Perl and Tcl. In this episode, Bart narrates ActiveState’s journey, including several pivots and ownership changes. Stay tuned to the end to find out how they were able to pivot to the open source thing that they do so well.

Transcript

Intro

Michael Schwartz: Hello, and welcome to Open Source Underdogs. I’m your host, Mike Schwartz, and this is episode 36 with Bart Copeland, CEO of ActiveState.

If you’ve ever installed Python, Perl, or Tcl on a Windows
workstation, there’s a pretty good chance you use the ActiveState installer and
distribution.

ActiveState is one of the oldest open-source companies in
existence. The founder was Dick Hardt, who some of you might know as one of the
editors of the OAuth 2.0 specifications, among other notable achievements.

This episode is the first one we’re publishing that was recorded
in person at the open-core summit. If you’re a fan of the podcast, you heard
Joe Jacks, a few episodes back, describing the event which did not disappoint.

Don’t miss the next one if you can get to San Francisco. Especially if you’re a founder or entrepreneur interested in open-source software development.

ActiveState made some major pivots, although I think they ended up
returning to their roots. It’s a pretty fascinating story. So, without further
ado, here we go. Bart, thanks for joining the podcast today.

Bart Copeland: Thank you, Mike, it is great to be here.

Origin

Michael Schwartz: ActiveState was founded in 1997, which makes it one of the oldest companies we’ve interviewed so far. It was acquired by Sophos, I guess in the 2000s, and then, it was bought out by management.

Just focusing on what happened after the acquisition, can you take
us back to the time after the buyout happened, and how you refocused a company?

Bart Copeland: It’s a really good question, Mike, but I should start with, in order to understand the refocus, we need to understand a little bit of history of why ActiveState was acquired in the first place.

ActiveState started in 1997, it was all around open source,
building specifically language distributions around open source for the
developers. Developers had needs specifically around Perl. Then, anti-spam
became a huge problem. ActiveState came up with an anti-spam solution called
Perl MX, and that caught the interest of Sophos.

Sophos acquired all of ActiveState, but Sophos really wanted the
Perl MX product, which eventually became PureMessage under Sophos. The CEO
Sophos had a lot of affinity, and pride, and admiration for all of ActiveState.
And the other team, the language distribution team, was dormant within Sophos,
and he did not want to do anything to hurt that team.

That’s where I got involved, and I was an early investor in
ActiveState, but I wasn’t part of management. But then, Steve Munford, the CEO
of Sophos, contacted me, and I, with a couple of few other outside investors,
we acquired the team, the technology, the customers and the ActiveState brand.

And what we wanted to do leaving Sophos, is, we wanted to do the
next great thing. We often said, “We want to do the next PureMessage.” So that
started us on what we refer to as chapter 2, or version 2.0 of ActiveState. So,
1.0 was 1997 to 2003. And then, 2.0 was after the dormant period, from 2003 to
2006. And 2006, that’s when we started ActiveState 2.0.

Maybe, before I go on, did I give you a good grounding of…?

Michael Schwartz: Sure. And what was the plan when you bought it out?

Bart Copeland: There was two key plans. The first key plan was, we needed to extract ourselves from Sophos. There’s all this infrastructure and technology overlap that we needed to distract ourselves from, so that was our first plan.

The second plan was, let’s go do the next great thing. And that’s
what we were going to do. We were a team, I think at the time, we were about 16
people or so. One other key caveat, above all this, was, I wanted to do it
organically. I didn’t want to raise a bunch of money. I said, “Let’s do this
the good old-fashioned way. Let’s drive revenue, let’s reinvest that revenue,
our profits into growing even further.” So, that was what we embarked on.

Value Prop

Michael Schwartz: Would you say that you’re similar to Anaconda, or RedHat, making an open-source software distribution, consumable by the enterprise, by providing reps and warranties, and liability protection, and patches, and aligning with the enterprise procurement process?

Bart Copeland: The short answer is — I’m going to give you two answers, the short answer and the long answer. The short answer is, I say, we do the same thing that RedHat does for Linux, but we do it for open-source programming languages. 

We have RedHat Enterprise Linux or RHEL, and it’s a
enterprise-grade distribution of Linux. We have Enterprise grade-distributions
for Perl, Python and Tlco, and there’s a lot more we’re doing there. That’s a
short answer.

The longer answer is, our whole mantra at ActiveState is twofold.
Mantra number one is, making open-source easy for the enterprise. Mantra number
two is, making open source that just works for developers.

When it comes to open source run times, whether you’re the
enterprise or the developer, there’s different needs. But if you look at the
complexity it is today, to build a language distribution from an open-source
ecosystem, and have that consistency across operating systems, managing all the
dependencies, managing the security issues, managing the license issues, and
then, keeping it updated, and making it really easy to deploy and share with
other developers, making it really easy to move that distribution from your dev
environment to your test environment, or your staging environment, or it’s your
production environment- it’s not easy.

We do a number of things that make it easy, as well as the
indemnification that you talk to. There’s really two audiences, there’s
developer audience and they have their needs, and then, there’s the Enterprise
audience and they have their needs. And our goal is to meet both audiences’
needs.

Revenue Streams

Michael Schwartz: So, from a revenue perspective, what are the most important products, and which products do you think are the most promising for future growth?

Bart Copeland: I talked about the versions or chapters of ActiveState. Under chapter 1, the most important product in terms of revenue potential and growth was Perl MX product.

Under chapter 2, it was the Stackato product. The Stackato was our
private PaaS offering. That product was sold to HP in 2015.

However, under chapter 3, it’s our language distributions product.
But here is the important thing to recognize, Mike. Under chapter 1, and
chapter 2, and under chapter 3, this has been a steady growing business, our
language distribution business. What we’re doing different under chapter 3, is
we’re trying to grow our business so that it doesn’t bifurcate. Because, if you
notice in chapter 1 and chapter 2, we ended up with two business units.

In chapter 1, we had the language distribution business, and we
had the Perl MX business. Under chapter 2, we had a language distribution
business, and then, this product called Stackato, which I touched on briefly.

So, we ended up with two business units under chapter 1 and
chapter 2, and I really felt what was important for us, as a company going
forward under chapter 3, is, let’s have a unified product offering, no
bifurcated businesses or two-business unit.

Our real growth opportunity and potential for ActiveState going
forward is around this whole area, what we refer to as open-source language
automation. This is a category that we’re leading in. It is bringing automation
to your open-source runtime.

And, as you know, Mike, in the hole open-source ecosystem today,
there is a lot of movement towards bringing automation to the software
development life-cycle. We are touching on one aspect of that, and that’s the
open-source runtime.

Why this is so important, and why we see this is a huge
opportunity, not only for ActiveState, for a lot of people in the open-source
ecosystem is that developers today have lost the freedom to do what they do
best, and that is, write code.

Developers today are spending more time doing things other than
writing code, they’re dealing with security issues, they’re dealing with
license compliance issues, they’re dealing with IT compliance issues, they’re
dealing with bug fixes. And it’s knowing that developers are losing their
efficiency in doing what they do best.

Furthermore, developers are not able to use the best tools to do
the job. What we’re trying to do, as a company, is to help free up developer,
so they have the right tools to do the best job, and they’re doing what they do
best and love to do, and that’s just writing code.

So, in summary to your question of, “Where is the biggest
potential for ActiveState?” – It’s around this whole category that we have
created called Open-source Language Automation.

Customer Segments

Michael Schwartz: ActiveState is serving many large customers, but the market for programming language is a very horizontal market, probably every company on the planet can use it. Do you segment the market in any way?

Bart Copeland: We do, and we don’t. There’s two ways we look at the market. The first way we look at the market is, we think of the developer, and we think of the large enterprise – we’re constantly thinking about that.

At ActiveState, we talked about bottom-up and top-down. Bottom-up
is, we think of the developer, and how do we create an experience for them, to
be very easy for them to consume our products and use them in working with us
quickly.

The top-down is, the developers using our product, bring it into
an enterprise, they bring it to their boss, and they say to the boss, “I really
like to use the ActiveState platform in greater detail at the job.” That’s the
top-down, it brings in the decision-maker, it brings the buyer. So, that is one
way we look at the market.

The other way we look at the market is, in terms of verticals, who has the greatest affinity for the types of solutions we build and sell. And historically, and going forward today, we’ve had a lot of success in obviously high-tech.

We’ve had a lot of success in banking and finance, we’ve had a lot
of success in aerospace and defense, we’ve had a lot of success in insurance,
and we’ve had a lot of success in manufacturing. Whereas we haven’t had a lot
of success for example in healthcare, to give you an example where we haven’t
had success.

But on the whole, though, we don’t do a lot of segmentations,
because you’re right, it’s a very horizontal play for us. And what we try to do
is, we try to make our softwares accessible to as many developers as we can
globally. Throughout the planet, we have downloads all over the planet. The
number one download is the US, and I think after that, our downloads are really
big in China and Japan, and then, in Europe.

Hopefully that gives you an idea of how we look at the
marketplace. And I guess, if I would really wear my marketing hat, we could do
a lot more segmentation that we’re doing than we’re not doing.

Sales Motion

Michael Schwartz: So, drilling down into the team a little bit, how do you organize the sales effort for such a global market? And how is that sort of adjusted over the years?

Bart Copeland: The first thing is actually, the adjustment has been the same under all versions of ActiveState, or all chapters of ActiveState, 1, 2 and 3. The selling motion has been the same. The selling motion from a sales organization is effectively comprised of account managers, account executives, and customer success managers, and inside sales reps, and depending on where you are in the selling cycle, involves those individuals.

Typically, what happens,
we — and I got the other aspect of sales engineers — we get a potential
opportunity. Usually, it comes from a developer, or group of developers, using
our solution within an organization. That then leaves to greater interest into,
going from the free version to a paid version. That involves an account
executive, with a sales engineer, they work together, and we do this all over
the phone.

All our selling is done
over the phone, rarely do we go on-prem to an organization. It’s done over the
phone, or through a series of video conference calls. Then, relationship is
made, a deal is consummated, all our deals are based on annual subscriptions.
That’s a recurring revenue model. Once the deal closes, then it goes to our
customer success manager.

The customer success
manager with her team, their job is to make the customer successful. Then,
there’s an account manager that is brought in to nurture and manage the
account, and renew it, and work with the account, to help them in other areas
of their business, where our solutions can help them. And that’s typically the
cycle that we work on.

Now, that is for the
Enterprise tier. One thing that I haven’t touched on, Mike, is that we, not
only have an Enterprise tier, we also have a lower-tier pricing structures. We
have five tiers, we have the Community Tier which is free, but then, we have
the Coder Tier, the Team Tier, the Business Tier, and the Enterprise Tier.

For the Coder Tier, Team
Tier and Business Tier, that’s handled by an inside sales group that deal with
the smaller price point products.

OEM

Michael Schwartz: I noticed that you have an OEM license – is that a material part of your business? And how did that come about?

Bart Copeland: Yeah. If you look at our business today, at the enterprise level, about 50% of the revenue at the enterprise level is enterprise subscriptions, and the other 50% is OEM. So, the way it came about is that when you get a distribution supported from ActiveState, there’s two ways you can consume that distribution. One way is, you consume it internally, and you consume it internally for all of your internal Dev practices or Dev applications that are enterprise wide.

However, another way you can consume our distributions is, you
bundle it with your product, and you sell that bundle to your end-users. For
example, you may have a product that requires a Python language distribution to
run your Python product on your customers’ systems.

Then, we OEM our language distribution as part of a bundle, and that’s how it came about. It’s a sizable portion of our business, the OEM portion.

Other Partnerships

Michael Schwartz: Are there other partnerships that you think are important to ActiveState?

Bart Copeland: So, going forward with the ActiveState platform, around open-source language automation, we feel the partnerships that are really important, it is right now looking at the whole landscape around CICD, around what GitHub and GitLab are doing, and what the cloud providers are doing, specifically AWS, Microsoft Azure and Google with Google Cloud platform, as well as we watch IBM Cloud, it’s kind of the number four cloud player.

Those are the three key partnerships. We’re looking at other areas
that we are concentrating aggressively. I would say there’s another area,
fourth area of a bunch of miscellaneous groups that we feel are important. For
example, we feel it’s very important to play well in the whole RedHat
ecosystem.

Another ecosystem we feel it’s important to play well is in the VMware ecosystem. Another very important area, which is more around standardization, is the Docker ecosystem, or the containerization ecosystem, to make it very easy to consume our distributions as containers.

Is ActiveState Open Core?

Michael Schwartz: You mentioned a few tiers of product – would you consider ActiveState distribution to be open core?

Bart Copeland: Absolutely, yes. If you look at what comes off of the platform, the ActiveState platform is all about building your language distribution, certifying it, and resolving.

So, when I say building, you decide which packages you want from
the open-source ecosystem, you decide which of the language runtime you want to
use from the open-source ecosystem. For example, to stick to Python, you want
Python 3.7, you want 35 packages from PyPI, you bring that all, and that’s all
open source.

We then build it for you, for the operating systems you care
about. You have three choices: Windows, Linux and Mac. You build it for the
operating systems you want. That then is created as a distribution, the core of
the distribution is open core, because it’s relying on all the open-source
licenses that exist, and we preserve that.

Once you build the distribution, then, we certify it, we check for
any “dependency hell” issues. What I refer to as dependency hell, we check for
any security violations, we check for any license issues that you may have
decided as a user, there’s certain licenses you don’t want.

The other thing we do is, we resolve any issues that come up
automatically in the background. You’ve got this distribution on the
ActiveState platform, and the result is, the dependency breaks or there’s a CV
threat – we fix that automatically and we alert you.

Where I’m going with this in the spirit of your question, all of
that is still open-core. It’s all based on all the open-source ecosystem, but
the platform itself is closed-core. That’s the closed proprietary layer on the
outside.

Pricing

Michael Schwartz: Over the years, have you significantly adapted your pricing strategy, or has it been relatively stable? Let’s just talk about the distributions, what you’re still in.

Bart Copeland: The distribution business has been relatively stable. The key thing that’s different is, historically, we’ve been distribution as-a-service. You come to ActiveState, and we provide you a distribution as-a-service. Now, we’ve evolved the business, where it’s, you self-serve with the platform and build your own distribution. It’s a software-as-a-service solution.

The pricing for the most part is the same, but we’re offering a
lot more for the same price now under the ActiveState platform.

Open Source With A Third-Party Project?

Michael Schwartz: One of our guests previously made the case that it’s better to sell open-source software that someone else writes because, otherwise, you are funding engineers who are basically not billable – would you agree with that?

Bart Copeland: Yes. But I think you have to find a fine balance. Because, if you are always taking and not giving – that’s not good. From my perspective, you have to have a very fine balance of how you’re dealing with the open-source ecosystems.

Language Support Roadmap

Michael Schwartz: There are new programming languages every year, it seems. I’m guessing if you’re a new programmer, you’re not going to start learning Perl or Tcl – has that made these products more valuable, maybe as you face less competition in the tools market?

Bart Copeland:  I believe it makes it worth value for two reasons. The first reason is what you mentioned. It is that we have a lot of legacy languages that we support, it is very important to the enterprise. Because, for example, and some of your listeners may laugh at this, is that we support today Perl 5.12.

We have Perl 5.28, but we have enterprises, we have applications
and production, and we support 5.12 for them, because it’s easier for them, if
we support Perl 5.12, to migrate to 5. 28.

So, in that sense, that’s very valuable to us and valuable to our customers. But at the same time, the same customers are saying, for new applications, for greenfield applications, we need to use the new languages, and can we go to ActiveState to get the new languages.

Our goal eventually, with the ActiveState platform, is to support any language that our customers want to use. We’re not there yet, but that’s the vision for the ActiveState platform.

Michael Schwartz: Which languages do you think you’re maybe in sooner than later?

Bart Copeland: Great question. Right now, we’ve got Perl, Tcl and Python. On a roadmap for coming up here is Javascript, and Ruby, and Java. And then, most likely were looking at PHP, R, Elm, Rust – these are some of the languages that are on our radar.

Team

Michael Schwartz: Can you talk a little bit about your approach to building the team? Does location weigh into the hiring equation, or are you willing to use remote people?

Bart Copeland: That’s a really good question. My philosophy is, we go where the talent is, we don’t force the talent to come to us. So, we are a company about — what is it today — think about it, just under 2/3 are head office in Vancouver. But I think it’s getting closer to 50%. The other 50% are distributed throughout North America.

Our philosophy is, as I said, we go where the talent is. And as a
result, especially on the development side, we are hiring developers, wherever
the talent is. We have developers spanning four different time zones, from West
Coast all the way to Halifax, which is one hour further than the East Coast
time.

But we tried to bookend it within those time zones, because we haven’t yet expanded to either the Asian market or the European market, just because of the collaboration. We wanted to be able to collaborate in real time. We use Slack aggressively as an organization.

So, the answer to your question is, we are very open to a
distributor organization. We think we’re doing a really good job of managing a
distributor organization. There’s a number of things we do to include all of
our virtual activators. We call ourselves activators at ActiveState. And we
refer to our remote activators as virtual activators or remotes.

Here’s some things we do to make them feel inclusive. We use Slack
aggressively. Most of our Slack channels are all public within the company, so
everybody can see what everybody’s doing. There’s freedom to lurk, there’s
freedom to participate.

We have regular company meetings once a month, with the entire
company, with video on. We also really encourage video meetings all the time.
Every morning, all the teams, various teams have daily stand-ups, the agile
methodology, all those daily stand-ups are done with video or a video
conferencing.

We also try to have all our activators, at least twice a year,
come to head office, so we fly everybody in. We have them all together, so they
can build relationships and cross-pollinate.

Also, many tech companies have a lot of nice fringe benefits, like
free drinks, free food, we bring in a warm lunch every Friday, we call it
“free-lunch Friday”. Unfortunately, our remote activators don’t have access to
that, so what we do is, we send them a food package once a month with Amazon
Prime — and I’m not sure exactly how we do it, I’m not involved with it myself
— but we actually ask them what they would like and we arrange it in an Amazon
Prime, and we deliver it to their homes.

And the other thing we do is, various members of the remote team
fly up on a regular basis to interact with the head office as well. These are
some of the things we do to promote inclusive environment, and also needs to
grow. Because it’s very hard, given the type of work they are doing, to find
all that talent in Vancouver – I would say it’s impossible. It’s not very hard
– it’s impossible.

Balance Free And Paid

Michael Schwartz: As a sort of Python hacker myself over the years, I’ve been on the ActiveState site a number of times, looking at code examples – how do you choose which efforts to invest in? And how do you invest, I guess the R&D or community work that you do – how do you prioritize it?

Bart Copeland: It’s a really good question. I don’t have a good answer for you on that. At the end of the day, we have to find a balance between investing in developers and solutions for developers and meeting their needs, and balance that with ultimately the enterprise, because they long-term pay the bills. And we need a healthy balance there.

One of the things I should touch on, Mike, is that, if you look at
ActiveState through its entire 20-year journey, there’s something common
through that 20-year journey. And that commonality is as follows: every single
product has been based on open source. Every single product has been built and
designed with the developer in mind. 

And every single product has been built with a developer and the
enterprise in mind. If they take the intersection of those three, that’s our
sweet spot, that’s where we make money. We’re constantly trying to find the
balance because we are a company that’s growing organically.

We don’t have outside money, we have to rely on our hard work and
creating a happy balance between developers, who don’t want to pay for things,
which we’re fine with, but finding and giving them those solutions that they’re
free to use, and then find that happy balance with developers and the
enterprise who are prepared to pay for what we offer.

How Far Do You Forecast?

Michael Schwartz: So, you’re 20 years in, which is not something a lot of tech companies can say – how far do you look ahead to the future? Are you looking 20 years out?

Bart Copeland: I look in three to five-year timeframes. Because if you look at ActiveState history, under ActiveState 1.0, we were focused on Perl, the high-rapid growth of Perl, and with the anti-spam problem under ActiveState 2.0, again we were focused on language distributions, and we were focused on the whole cloud computing space, and specifically for us, platform-as-a-service.

Now, we’re focused on open-source language automation and helping
make software really work well for developers in the next three to five years.

Because tech moves so fast, the industry is so vibrant and so exciting.
And I often say to younger developers, younger people getting into tech –
because I’ve been it now for 30 years– I say, “We are still in the early
innings. We’re like an inning 2.”

If somebody said to me this is a 100-year cycle we’re in right now
in tech, and we’re still in it 20 years or so, we got a lot to do. It’s just
starting to get exciting. I’m kind of looking here, I’m at the

the latter part of my career, and I’m looking at my two young
sons, who are just starting their careers, and I want to do it all over again.

Because I think it’s going to get even more exciting. But the
point I’m trying to make here, Mike, it’s very hard to look beyond three to
five years in my view. We, right now, are focused on this audacious goal of
building a platform for open-source runtimes and specifically solving the
problem around open-source language automation. That’s our focus, that’s a
three to five-year plan. We’re going to deliver on that, and then we’ll regroup
again.

Bootstrap Governance

Michael Schwartz: Quick question on governance. As a bootstrap company, do you have a board of directors? What does governance look like in a bootstrapped company?

Bart Copeland: Bootstrap company, by definition, that means we’re a private company. So, the company is owned by its employees and some key shareholders. And I believe in good corporate governance, and there is a board. The board is comprised of some of the key shareholders – it’s a very small board.

I think it’s important, as a CEO, that you get external advice, so
in addition to having a board, because that’s one form of advice, I have a
group of advisers that advise me as well and advise my leadership team.

And I think that’s very important. I think as a bootstrap company,
you shouldn’t do things in isolation. It’s very important that you have
individuals that are not in the trees with you, and they can constantly spot
and say, “Hey Bart, have you considered this, or what about that?”

There’s four of us on the board. And then, I have three other advisers, who are not part of the board, but advise me one-on-one.

Advice For Open-Source Entrepreneurs

Michael Schwartz: Last question. Any advice for new entrepreneurs, who are launching a business around an open-source software project?

Bart Copeland: Oh, that’s a good question, Mike. I think there’s a general advice, and then there is advice specific to open source. The general advice that I give — and I do a lot of Angel Investing with young entrepreneurs, and invest in small promising individuals and companies — the advice I give is, persistence, and perseverance and focus.

If you believe in
something, stay at it. Don’t lose your focus. That doesn’t mean you shouldn’t
pivot, but if you look at people who are successful – it’s about perseverance
and persistence. That’s the general advice.

As far as open source is
concerned, I think my advice is, I love open source. It IS the future. When I
first started an open source, people were saying, “This crazy. Why are you
doing open source? There’s no future in it.” Now, open source has one. There’s
so much power in collaboration in open source.

My advice is, if you are
not using open source, then there’s something wrong with your company. You
should BE using open source. It’s the way to go. It is the de-facto standard to
build a great organization.

Michael Schwartz: Bart, that was fantastic. Thank you so much for joining us today.

Bart Copeland: Thank you, Mike, it’s been great.

Michael Schwartz: Thanks to Bart and the ActiveState team for making this interview happen. Thank you, thank you to the Open Core Summit team for giving us a table at the event to promote the podcast, and for giving up their sponsorship room a few times, which was the quietest place we could find to record.

Please, support the
event. We need more events like this to grow the industry and to share our
experiences in person.

Transcription and episode audio can be found on opensourceunderdogs.com.

Music from Broke For
Free and Chris Zabriskie.

Audio editing by Ines
Cetenji.

Production assistance
and transcription by Natalie Lowe. Operational support from William Lowe.

Have comments? Tweet at us. Our Twitter handle is @fosspodcast.

Please subscribe to the
podcast and add it to your favorites on your podcast app. That helps us get the
word out.

Next week, we have Ben Golub from Storj, who will take us through the first open-source, blockchain business model.

Until then, thanks for
listening.

The post Episode 36: ActiveState – Open Source Languages Platform with Bart Copeland first appeared on Open Source Underdogs.