<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>opsZero Blog</title>
        <link>https://opsZero.com/blog</link>
        <description>opsZero Blog</description>
        <lastBuildDate>Wed, 15 Apr 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[v10.2: Spring Cleaning]]></title>
            <link>https://opsZero.com/blog/2026/04/15/v10.2-spring-cleaning</link>
            <guid>https://opsZero.com/blog/2026/04/15/v10.2-spring-cleaning</guid>
            <pubDate>Wed, 15 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[We have done some general spring cleaning on the backend. We have accumulated a]]></description>
            <content:encoded><![CDATA[<p>We have done some general spring cleaning on the backend. We have accumulated a
lot of cruft over the years and the time was getting right for us to make the
technical debt clean up. Some of the mistakes we did was to make microservices
of those that need to be monoliths and monoliths out of those that need to be
microservices.</p>
<p>To say all of this was getting a bit complex to manage is an understatement.
Instead of serving our customers which is what technology is supposed to allow
we were serving busywork. Things that look like they are important to do but
actually don't provide a whole lot of value.</p>
<p>A lot of these are gone helping reduce context switching costs.</p>
<p>Some specifics of the cleanups that we have done:</p>
<ul>
<li class="">Our sales scrapers are now their own microservices. We find that datasets are
better if they exist independently of the main code. There is just added complexity
of managing a bunch of different scrapers.</li>
<li class="">Unified billing that manages our Stripe and Mercury invoicing across our
different products.</li>
<li class="">Standardized interfaces to connect to our vendors instead of multiple
independent implementations.</li>
</ul>
<p>I know doesn't seem like a lot but it is simple things like this that cruft up over
time as the SaaS tooling that is used changes.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v10.1: New Business Number]]></title>
            <link>https://opsZero.com/blog/2026/04/07/v10.1-new-business-number</link>
            <guid>https://opsZero.com/blog/2026/04/07/v10.1-new-business-number</guid>
            <pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[We now have a new business number +1-925-917-5662 and can now be contacted]]></description>
            <content:encoded><![CDATA[<p>We now have a new business number +1-925-917-5662 and can now be contacted
through Text, WhatsApp &amp; Signal. We hope this allows us to communicate with you
whenever you need us and be available in real time. We have found that we have
been struggling with VOIP solutions as they don’t allow us to have the texting
capabilities that our customers want. So we have decided to move to a solution
that allows us to provide mobile responses.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v10.0: Ten Years in Business]]></title>
            <link>https://opsZero.com/blog/2026/04/01/v10.0-ten-years-in-business</link>
            <guid>https://opsZero.com/blog/2026/04/01/v10.0-ten-years-in-business</guid>
            <pubDate>Wed, 01 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Ten years in business! We are a dinosaur in terms of tech years but we are]]></description>
            <content:encoded><![CDATA[<p>Ten years in business! We are a dinosaur in terms of tech years but we are
running strong and planning for the next ten. As AI has disrupted the industry
we have been pushed to figure out how opsZero lives in this new world. While
there has been messaging that the recent layoffs are due to AI, we don’t ascribe
to that. The period of low interest rates caused a spike in hiring for a growth
that never materialized and the layoffs are the culmination of a failure of that
bet. The CapEx on AI doesn’t help but AI is becoming a convenient reason to
perform layoffs.</p>
<p>While we are bullish on AI in the long run, the AI currently is still in the 90s
dotcom phase. Who the winners will be are still up in the air and there is a
massive amount of investment money sloshing around so the eventual winner may
come out of left field. However, the recent Iran war will push energy prices up
leading to the unit economics of AI being disrupted. This is not to say AI will
not be used, it just means that it will be used within specific fields: defense
and healthcare being the two primary areas. With energy prices going up due to
the Iran War, datacenters and their consequential increase in energy prices will
not sit well with citizens.</p>
<p>Further, the SaaSocolypse, attributed to the increased effectiveness of AI, has
pushed down the value of SaaS companies which are also loaded up with an immense
amount of debt due to Private Credit. We will see if this leads to a crash in
the market, but this does fundamentally changes the nature of American SaaS. The
gulf countries are a massive investor in the technology industry in the US
investing heavily into AI through private equity, private credit, and the public
markets. With these countries now questioning the value of the petrodollar, the
future of investments from these countries is looking wobbly especially when
these countries can invest in other countries with a potential for higher
returns. This is also based on a notion that these countries will return back to
normal once the war is completed.</p>
<p>It is this economic environment that opsZero finds itself trying to plan for its
second decade. It is when the World Order changes that one can find immense
opportunities. As the structures of the old order cease, new ones are formulated
with new rules in play. And the place we find ourselves in at this particular
moment is the collapse of the dollar.</p>
<p>All signs point to the American dollar losing value, scarcity of resources, and
stagflation. While we have seen the first order effects of the Iran War which
are higher gas and diesel prices we haven’t seen the second and third order
effects. From an American standpoint, food prices will go up, medicine prices
will go up because nearly 40% of medicine in America comes from India, there
will be metal and aluminum shortages, if Hormutz stays closed and Helium doesn’t
get through there will be microchip shortages. These shortages can be temporary,
a year or two, or can be extended. It all depends on the extent of the damage
that results from an eventual ground invasion.</p>
<p>opsZero never became a SaaS company preferring the path of services. While this
limited our upside in terms of revenue, it has made us nimble and able to change
directions as the winds of the economy change. We believe that many SaaS
companies will convert to being services companies in the future. With AI, SaaS
will need to customize for a particular customer, not just sell a one size fits
all. This will be, ironically, a return to the traditional business model of
Oracle, IBM, or SAP that focus heavily on customizing their offerings for their
Fortune 500 customers.</p>
<p>As AI changes the nature of the game on how quickly companies can be formed, we
have moved to a world where small efficient companies will be the norm.
Companies with fewer customers as there will be more competition, but customers
with deeper focus. In a sense, future SaaS companies are going to become
traditional businesses with a large service components, they will not be
traditional VC hypergrowth companies. We can say that this is caused completely
by AI, but with less capital to go around this will become more the norm in
terms of business.</p>
<p>So opsZero is going to double down on our services model as it is the model for
the next decade. We are doubling down on our investment in India. As the cost of
capital goes up, the inevitable outcome is a lowering of costs and
India provides a better cost structure compared to the West. The recent
layoffs in America have not lead to any mass layoffs in India, for example.
Lastly, we believe that services will be accelerated with technology being in
support. So whether there is a Human or AI being the frontend there will still
be technology in the backend.</p>
<p>The outcome of this is that organizations will want Human, AI, and Software as
part of their expected interaction while being provided that value at a lower
cost. How we deliver this will be a blog post a decade from now.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.11.1: Existing SaaS Offerings Deprecated!]]></title>
            <link>https://opsZero.com/blog/2026/03/24/v9.11.1</link>
            <guid>https://opsZero.com/blog/2026/03/24/v9.11.1</guid>
            <pubDate>Tue, 24 Mar 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[As noted before all of our existing SaaS tooling has been merged back into opsZero. This table includes the existing businesses and their new opsZero location:]]></description>
            <content:encoded><![CDATA[<p>As noted before all of our existing SaaS tooling has been merged back into opsZero. This table includes the existing businesses and their new opsZero location:</p>
<table><thead><tr><th style="text-align:left">Existing</th><th style="text-align:left">New</th></tr></thead><tbody><tr><td style="text-align:left"><a href="https://dbazero.com/" target="_blank" rel="noopener noreferrer" class="">https://dbazero.com</a></td><td style="text-align:left"><a href="https://opszero.com/solutions/dba" target="_blank" rel="noopener noreferrer" class="">https://opszero.com/solutions/dba</a></td></tr><tr><td style="text-align:left"><a href="https://deepfacts.ai/" target="_blank" rel="noopener noreferrer" class="">https://deepfacts.ai</a></td><td style="text-align:left"><a href="https://opszero.com/solutions/ai" target="_blank" rel="noopener noreferrer" class="">https://opszero.com/solutions/ai</a></td></tr><tr><td style="text-align:left"><a href="https://discountcloud.io/" target="_blank" rel="noopener noreferrer" class="">https://discountcloud.io</a></td><td style="text-align:left"><a href="https://opszero.com/solutions/finops/savings" target="_blank" rel="noopener noreferrer" class="">https://opszero.com/solutions/finops/savings</a></td></tr><tr><td style="text-align:left"><a href="https://policycop.com/" target="_blank" rel="noopener noreferrer" class="">https://policycop.com</a></td><td style="text-align:left"><a href="https://opszero.com/solutions/compliance" target="_blank" rel="noopener noreferrer" class="">https://opszero.com/solutions/compliance</a></td></tr><tr><td style="text-align:left"><a href="https://kubespot.com/" target="_blank" rel="noopener noreferrer" class="">https://kubespot.com</a></td><td style="text-align:left"><a href="https://opszero.com/solutions/kubernetes" target="_blank" rel="noopener noreferrer" class="">https://opszero.com/solutions/kubernetes</a></td></tr></tbody></table>
<p>Our goal is to provide more value by incorporating each of these into core opsZero.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.11.1: Consolidation of opsZero!]]></title>
            <link>https://opsZero.com/blog/2026/03/23/v9.11.0</link>
            <guid>https://opsZero.com/blog/2026/03/23/v9.11.0</guid>
            <pubDate>Mon, 23 Mar 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[We have merged our different products into eight solutions that are under the]]></description>
            <content:encoded><![CDATA[<p>We have merged our different products into eight solutions that are under the
opsZero umbrella. We have always been a DevOps Agency and while we wanted to
move towards a SaaS model we realized that we just enjoy the services business
model. It allows us to get more involved with our customers versus just trying
to optimize for cash flow, and we really just want to help our customers in a
broader way than what a pure SaaS model would entail.</p>
<p>Further, we believe that SaaS has become saturated. There is a SaaS solution for
nearly everything and we are getting to a point of diminishing returns. We
missed the boat on the SaaS train, but honestly we are not super worried about
it. We think embedding deeper with customers and becoming long term partners is
more meaningful for us.</p>
<p>So we are largely deprecating our existing SaaS tooling and moving back to what
we are at our core: a DevOps Agency.</p>
<p>Our focus is not high growth, but sustainable growth working at a steady pace
helping our customers throughout their growth. This model is antithesis is
complexity. We actually want to reduce the complexity of our offering.</p>
<ul>
<li class=""><strong>DevOps.</strong> The basis of our go to market. We do all DevOps with OpenTofu/Terraform as the basis.</li>
<li class=""><strong>Kubernetes.</strong> Kubernetes is our bread and butter. We will focus on making this the core of our value. Moving Windows, Linux, etc. workloads to Kubernetes is a primary goal.</li>
<li class=""><strong>Identity.</strong> Setup and manage identity solutions.</li>
<li class=""><strong>Compliance.</strong> Focusing on HIPAA, SOC2, PCI-DSS, etc.</li>
<li class=""><strong>Datasets.</strong> Build and host core datasets for companies that want to use these for their own specific use cases.</li>
<li class=""><strong>DBA.</strong> Database and performance tuning to lower the cost of compute for companies.</li>
<li class=""><strong>AI.</strong> Low cost AI compute solutions such as running workloads on Macs, etc.</li>
<li class=""><strong>FinOps.</strong> Resale business, but we will likely limit to just the Cloud.</li>
</ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.10: opsZero DBA says Hello world!]]></title>
            <link>https://opsZero.com/blog/2026/01/20/v9.10</link>
            <guid>https://opsZero.com/blog/2026/01/20/v9.10</guid>
            <pubDate>Tue, 20 Jan 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Introducing DBAZero!]]></description>
            <content:encoded><![CDATA[<p>Introducing DBAZero!</p>
<p>We are launching a database and performance tuning service designed for startups
and small businesses. We found that many companies struggle with database
performance tuning and management and we want to help them focus on their core
business while we handle the database side of things.</p>
<p>As part of this we are launching our service with a focus on the following:</p>
<ul>
<li class="">DB performance improvements.<!-- -->
<ul>
<li class="">Database Performance Tuning</li>
<li class="">Schema Review</li>
<li class="">DB Modeling</li>
<li class="">Table Design</li>
<li class="">Query Review and Tuning</li>
<li class="">Indexing</li>
<li class="">Transactions and Locking</li>
<li class="">Concurrent Query performance</li>
<li class="">Read vs Write Tradeoffs</li>
<li class="">Stored Procedures</li>
<li class="">Views</li>
</ul>
</li>
<li class="">Outside of DB performance<!-- -->
<ul>
<li class="">Data Analytics</li>
<li class="">Data Science on tabular data</li>
<li class="">time series modeling</li>
<li class="">Python/R programming</li>
</ul>
</li>
</ul>
<p>We will be sharing more details about our services and how we can help.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.9: AWS Sales Collaboration]]></title>
            <link>https://opsZero.com/blog/2025/10/28/v9.9</link>
            <guid>https://opsZero.com/blog/2025/10/28/v9.9</guid>
            <pubDate>Tue, 28 Oct 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[We’ve updated our sales process to automatically create AWS ACE opportunities —]]></description>
            <content:encoded><![CDATA[<p>We’ve updated our sales process to automatically create AWS ACE opportunities —
a system that allows us to seamlessly collaborate with AWS sales representatives
on opsZero’s opportunities.</p>
<p>This integration means we can now work directly with AWS account managers from
the very beginning to identify the best solutions for your needs. It also
enables us to bring in AWS Solutions Engineers early in the process to address
technical challenges more efficiently.</p>
<p>While this change happens mostly behind the scenes, it significantly enhances
our ability to problem-solve and deliver better outcomes for our customers
during the sales process.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.8.5: Enhanced Task Management]]></title>
            <link>https://opsZero.com/blog/2025/10/24/v9.8.5</link>
            <guid>https://opsZero.com/blog/2025/10/24/v9.8.5</guid>
            <pubDate>Fri, 24 Oct 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[We have revamped our support task management system to improve clarity and]]></description>
            <content:encoded><![CDATA[<p>We have revamped our support task management system to improve clarity and
efficiency. One of the key changes we have implemented as part of this new
system is a deprecation of Notion as our task management tool and a migration to
GitHub Issues and Github Projects internally while ensuring that our customers
can continue using their existing project management tools like Notion, Jira,
Linear, Github Issues, etc.</p>
<p>Github Issues is what we use anyways for our product development tasks and this
change allows us to simplify our internal processes and have a single source of
truth. Further, we can now also leverage Github Actions to automate many of our
routine tasks.</p>
<p>Lastly, we are in general improving out task management processes to ensure that
tasks are completed in a timely manner and nothing slips through the cracks as
part of this setup we have standardized our processes into a global Kanban board
that tracks the changes that affect our customers and the internal development
of tasks so that work can be completed in lockstep.</p>
<p>This has been a long time coming and we are excited to roll this out.</p>]]></content:encoded>
            <category>DevOps</category>
        </item>
        <item>
            <title><![CDATA[v9.8: AWS Offerings]]></title>
            <link>https://opsZero.com/blog/2025/10/22/v9.8</link>
            <guid>https://opsZero.com/blog/2025/10/22/v9.8</guid>
            <pubDate>Wed, 22 Oct 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[We now have a variety of AWS offerings on the AWS APN Marketplace and have made]]></description>
            <content:encoded><![CDATA[<p>We now have a variety of AWS offerings on the AWS APN Marketplace and have made
it easy to add new offerings. These offerings allow us to get in front of AWS
account managers with our products and services so they can recommend us to
their customers.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.7: CI/CD Infrastructure]]></title>
            <link>https://opsZero.com/blog/2025/10/14/v9.7</link>
            <guid>https://opsZero.com/blog/2025/10/14/v9.7</guid>
            <pubDate>Tue, 14 Oct 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[opsZero now has a full CI/CD setup for all our products and services. These are]]></description>
            <content:encoded><![CDATA[<p>opsZero now has a full CI/CD setup for all our products and services. These are
setup on Django for the API and Docusaurus for the frontend with Cloudflare
Pages for hosting. Previously we only had CI/CD setup for some of our
applications which made consistency of releases a bit problematic.</p>
<p>It is ironic we know that a DevOps company didn't have a full CI/CD setup for
our apps. However, I don't think CI/CD is necessary to get things going and we
can make a lot of progress without it. We needed to prove our products had value
first before we invested time into setting up the CI/CD pipelines and other
tooling.</p>
<p>Now that we have a standardized process in place we can focus on releasing our
products more frequently and with more confidence.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.6: Your Cloud + AI Team]]></title>
            <link>https://opsZero.com/blog/2025/09/09/v9.6</link>
            <guid>https://opsZero.com/blog/2025/09/09/v9.6</guid>
            <pubDate>Tue, 09 Sep 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[opsZero is getting a large refresh across both opsZero as well as on our various]]></description>
            <content:encoded><![CDATA[<p>opsZero is getting a large refresh across both opsZero as well as on our various
brands. As we <a class="" href="https://opszero.com/blog/2025/09/08/v9.5">stated before</a> we are splitting apart our
business to have their own identities. As part of this we decided to structure a
common design across all our businesses. This allows us to create new businesses
in the future with a common templates. While this work is ongoing we are quite
excited to announce it now as a significant portion of the sites have been
updated to use these new templates.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.5: Partnership Based Growth]]></title>
            <link>https://opsZero.com/blog/2025/09/08/v9.5</link>
            <guid>https://opsZero.com/blog/2025/09/08/v9.5</guid>
            <pubDate>Mon, 08 Sep 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[opsZero will release products and grow our business through mutually beneficial]]></description>
            <content:encoded><![CDATA[<p>opsZero will release products and grow our business through mutually beneficial
partnerships. Our business is Cloud Infrastructure and our long term plan is to
become a Platform for Cloud + AI. However, each vertical has domain specific
knowledge we lack and do not have a large team while limits our reach.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="partnerships">Partnerships<a href="https://opszero.com/blog/2025/09/08/v9.5#partnerships" class="hash-link" aria-label="Direct link to Partnerships" title="Direct link to Partnerships" translate="no">​</a></h2>
<p>When I look at opsZero's failures it has been largely around going into new
verticals alone. If opsZero goes at a vertical alone we had to figure out the
market, the marketing, and sales. It creates the onus on us to deliver and sell
and learn a new industry. Even if we move horizontally within an industry we
will still need to context switch as we sell from startups to governments to
healthcare. This prevents us from focusing on a single vertical making our
growth feel haphazard and lacking focus. We need teams single threaded focused
on each vertical.</p>
<p>Traditionally, a company that wants to grow its business either hires people
with expertise to build that business or buys a business that has those
relationships. The problem with that is it becomes a capital expenditure where a
failure means a total loss, partnerships allow us to make entering new verticals
an operational expenditure. This reduces the cost of launching and testing
something new and attacking it with people who are already knowledgeable.</p>
<p>Our goal long term with opsZero is to build a bazaar style platform servicing
the needs of multiple verticals cobuilt with partners. We will become a
distribution focused company with the current services becoming another
“partner” within the ecosystem. Our buckets are Cloud and AI. All our products
and services should live within these two buckets. And each service we release
should have a partner who is responsible for servicing it.</p>
<p>This changes the organizational structure of the company to be like a startup
studio or incubator. While we should sell a cohesive whole to our customers,
behind the scenes it can be our partners who service the end result for a
particular vertical while we complement them with our value add.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="solutions">Solutions<a href="https://opszero.com/blog/2025/09/08/v9.5#solutions" class="hash-link" aria-label="Direct link to Solutions" title="Direct link to Solutions" translate="no">​</a></h2>
<p>Our release methodology will change to the following:</p>
<ul>
<li class="">Figure out the service we want to create for a vertical.</li>
<li class="">Find partners who could be good fits for coselling that product. Figure out
ways we can partner with them.</li>
<li class="">Cobranded and create a joint venture and cosell with partner. Focus on
distribution and support the partner with data and sales resources.</li>
<li class="">Continuously work with partner to more effectively reach customers and service
the work for the customers.</li>
</ul>
<p>The things we can do with a partner are three fold:</p>
<ul>
<li class="">Comarketing such as content, webinar, videos or other.</li>
<li class="">Build new products that combines our strengths.</li>
<li class="">Emails or other joint collaboration.</li>
<li class="">Products</li>
</ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.4: Services First to Product First]]></title>
            <link>https://opsZero.com/blog/2025/09/03/v9.4</link>
            <guid>https://opsZero.com/blog/2025/09/03/v9.4</guid>
            <pubDate>Wed, 03 Sep 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[For the last decade opsZero has been a service’s first business. We built up a]]></description>
            <content:encoded><![CDATA[<p>For the last decade opsZero has been a service’s first business. We built up a
repository of deep knowledge about the Cloud and AI and accumulated various
partnerships to boot. However, the problem is what does opsZero do becomes
harder to explain. We do so many different things as a services company that it
is becoming impossible to explain to customers what we do concisely.</p>
<p>So to both simplify the business and to make it easier to explain to potential
customers our value we are breaking apart opsZero into various parts:</p>
<ul>
<li class="">Kubespot</li>
<li class="">DiscountCloud</li>
<li class="">DBAZero</li>
<li class="">OMYAC</li>
<li class="">PolicyCop</li>
<li class="">deepfacts.ai</li>
</ul>
<p>Yes, we are splitting opsZero into five specialized businesses.</p>
<p>Second, we are turning these businesses into product first businesses. This
allows us to build out our offerings in scalable ways with focused leadership on
each product and a set of KPIs that allow each business to scale independently.</p>
<p>At this point we have leadership for each of these subbusinesses including Sohan
for Kubespot, Lokesh for DBAZero, Swarup for DiscountCloud, and Vamsi for
deepfacts.ai. We are excited to see how we can scale each of these businesses.</p>
<p>So what does this mean for opsZero?</p>
<p>opsZero is becoming a company focused on bringing cloud native software to
market. While we are starting with the five new products our long term goal is
to bring additional products to market.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.3: Standardizing on Docusaurus]]></title>
            <link>https://opsZero.com/blog/2025/08/25/v9.3</link>
            <guid>https://opsZero.com/blog/2025/08/25/v9.3</guid>
            <pubDate>Mon, 25 Aug 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[All websites are now standardized on Docusaurus. This allows us to more easily]]></description>
            <content:encoded><![CDATA[<p>All websites are now standardized on Docusaurus. This allows us to more easily
manage and maintain our ventures. With the usage of Docusaurus we can now easily
share code and content between ventures and allow for a more consistent go to
market across all ventures.</p>
<p>While Docusarus doesn’t have all the bells and whistles of other frameworks like
NextJS, etc. it is a framework that does get out of the way.  opsZero site has
been migrated from WordPress to now being hosted on Cloudflare Workers using
Docusaurus. Docusarus can be used to make any pages not just documentation
sites. Further, it is opinionated in the way it is structured which is what we
like, a standardized way of organizing content across all the new ventures we
are looking to launch such as DiscountCloud.io</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.2: Google Analytics]]></title>
            <link>https://opsZero.com/blog/2025/08/20/v9.2</link>
            <guid>https://opsZero.com/blog/2025/08/20/v9.2</guid>
            <pubDate>Wed, 20 Aug 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[We now have a Google Analytics integration to allow us to track website visitors]]></description>
            <content:encoded><![CDATA[<p>We now have a Google Analytics integration to allow us to track website visitors
for our ventures using the Deming Control Chart methodology. While this is not
exactly an exciting feature, it is our first integration point for monitoring
and track venture metrics.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.1.3: AWS Cosell]]></title>
            <link>https://opsZero.com/blog/2025/07/10/v9.1.3</link>
            <guid>https://opsZero.com/blog/2025/07/10/v9.1.3</guid>
            <pubDate>Thu, 10 Jul 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[We now have a lead list filtering feature to allow us to cosell with AWS. This]]></description>
            <content:encoded><![CDATA[<p>We now have a lead list filtering feature to allow us to cosell with AWS. This
lead list filtering now allows us to find opportunities across the AWS ecosystem
for startups and SLED for us to perform outreach.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.1.2: Vanta Cosell]]></title>
            <link>https://opsZero.com/blog/2025/07/01/v9.1.2</link>
            <guid>https://opsZero.com/blog/2025/07/01/v9.1.2</guid>
            <pubDate>Tue, 01 Jul 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[We are excited to announce that we are now closely working with Vanta. As]]></description>
            <content:encoded><![CDATA[<p>We are excited to announce that we are now closely working with Vanta. As
a partner of Vanta, we are able to offer our customers a streamlined
experience for managing their security and compliance needs. We are able
to provide our customers with a comprehensive solution that includes
security monitoring, compliance management, and risk assessment.</p>
<p>As part of this partnerships:</p>
<ul>
<li class="">We are now reselling Vanta as an MSP.</li>
<li class="">We have a close relationship with Vanta's sales team.</li>
<li class="">We are building custom integrations with Vanta to streamline any issues.</li>
</ul>
<p>With this we are combining the sales processes of MakeProspect with the
compliance remediation of PolicyCop.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.1.1: Lead List Filtering]]></title>
            <link>https://opsZero.com/blog/2025/06/30/v9.1.1</link>
            <guid>https://opsZero.com/blog/2025/06/30/v9.1.1</guid>
            <pubDate>Mon, 30 Jun 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[For the v1.1.1 release of MakeProspect we are focusing on the lead list]]></description>
            <content:encoded><![CDATA[<p>For the v1.1.1 release of MakeProspect we are focusing on the lead list
filtering, onboarding companies onto our platform, and setting up the WhatsApp
groups that we use to interact with customers. Lastly, we are focusing in on
the campaigns feature to start building out the outreach capabilities.</p>
<p>Overall this is an internal release and not an external feature release.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.1.0.1: Healthcare AI Dev Team]]></title>
            <link>https://opsZero.com/blog/2025/06/27/v9.1.0.1</link>
            <guid>https://opsZero.com/blog/2025/06/27/v9.1.0.1</guid>
            <pubDate>Fri, 27 Jun 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[We are building a team to support the requirements of AI in healthcare. This new]]></description>
            <content:encoded><![CDATA[<p>We are building a team to support the requirements of AI in healthcare. This new
organization is called <a href="https://deepfacts.ai/" target="_blank" rel="noopener noreferrer" class="">Deepfacts.ai</a>. We have signed up
our first customer and are looking to develop and expand the capabilities around
a core set of features.</p>
<p>We are getting started with a few areas of focus:</p>
<ul>
<li class="">AI Model Development</li>
<li class="">AI Agents</li>
<li class="">MCP servers</li>
<li class="">Python APIs</li>
</ul>
<p>With this additional capability we are able to provide additional platform
engineering capabilties to healthcare customers.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[v9.1.0: Fixing the Real Compliance Pain]]></title>
            <link>https://opsZero.com/blog/2025/06/20/v9.1.0</link>
            <guid>https://opsZero.com/blog/2025/06/20/v9.1.0</guid>
            <pubDate>Fri, 20 Jun 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[Getting compliant with SOC 2, HIPAA, or PCI-DSS is a huge time sink—especially]]></description>
            <content:encoded><![CDATA[<p>Getting compliant with SOC 2, HIPAA, or PCI-DSS is a huge time sink—especially
for developers. Most compliance tools surface issues, but they don’t actually
fix them. And most auditors stop at pointing things out, leaving engineering
teams to figure out the rest.</p>
<p>That’s where <a href="https://policycop.com/" target="_blank" rel="noopener noreferrer" class="">PolicyCop</a> comes in.</p>
<p>We built PolicyCop because we were tired of wasting engineering time chasing
down infrastructure misconfigurations and writing glue code to make compliance
tools like Vanta work properly. Most of what’s considered “compliance work” is
really just boring infrastructure cleanup and automation that no one wants to
do—but someone has to.  PolicyCop handles:</p>
<ul>
<li class=""><strong>Fixing non-compliant infrastructure</strong>: We don’t just point out problems—we go in and remediate them.</li>
<li class=""><strong>Custom API integrations for Vanta</strong>: We write the missing pieces so your infrastructure reports correctly.</li>
<li class=""><strong>Vanta Resale</strong>: If you’re using (or planning to use) Vanta, we can help you set it up right and keep it working.</li>
</ul>
<p>Compliance is still annoying. But with PolicyCop, at least the worst parts don’t
land on your dev team’s plate.</p>]]></content:encoded>
        </item>
    </channel>
</rss>