Nexus – Nexus is a repository manager which allows the proxy, collect and manage the dependencies.
It makes it easy to distribute the software.

Nexus is best to organize, store and distribute software components.

It delivers safer, faster, and better software with an automated software supply chain.

The Sonatype Nexus is an open-source tool which having 527 GitHub stars and 237 GitHub forks.

The Nexus platforms are more than 80% accurate than Jfrog Artifactory. Nexus provides universal support and is suitable with popular tools like Eclipse, Hudson, Jenkins, Puppet, Chef, Docker Etc.

Nexus has vast format coverage and supports all important languages and ecosystems.

Nexus repository is a robust package registry to all docker images and Helm chart repositories.

Artifactory – Artifactory is a universal repository manager. It integrates with the ecosystem and manages binaries and provides consistency to CI/CD workflow.

Artifactory is a tool that collaborates codes and version control. It supports all types of available software packages, enabling automated continuous integration and delivery.

Artifactory discloses a vast REST API that offers access to its features in the development cycle. Through API it is possible to manage builds, repositories, and artifacts and can perform searches, apply configurations, perform maintenance tasks, and many more.

Artifactory Query Language (AQL) gives you unusual flexibility to search for artifacts. It provides the easiest way to prepare queries that state any number of search criteria, filters, sorting options, and output fields.

Artifactory manages, configure and monitor DevOps services in the organization through a single pane of glass.

Differences between Sonatype Nexus and Artifactory

Artifactory is a tool that can be classified in the ‘Code Collaboration & Version Control’ category, whereas Sonatype Nexus is grouped under ‘Java Build Tools’.

According to the StackShare community, Sonatype Nexus has a wider approval, being mentioned in 49 company stacks and 16 developers stacks in comparison to JFrog Artifactory, which is listed in 16 companies stacks and 11 developer stacks.

Artifactory provides multi-cloud as well as hybrid cloud solutions whereas Nexus only supports on-prem.

Artifactory offers all the rest of the API endpoints which is needed for development, QA/QC, CI/CD, distribution, and deployment processes which Nexus doesn’t.

Artifactory stores exhaustive build-information for all builds (software bill of materials, or SBOM), it hosts and provides artifactory Query Language (AQL), an easy, and highly flexible tool to search for artifacts based on this ampleness of meta-data. There is no other repository manager that provides such extensive use of meta-data even Nexus as well.

Artifactory supports all major cloud storage providers (AWS, GCS, Azure Blob storage) and filestore sharding as well. But unfortunately, Nexus doesn’t support all these.

Artifactory supports a variety of replication modes ( pulled replication through a remote proxy, Active push replication to a single target, Active simultaneous push replication to multiple targets, event-based pull replication ) to support the different multi-site topologies of your global DevOps processes. Nexus only support pull replication through remote proxy.

Artifactory uses Derby DB by default whereas, Nexus uses a file system to store artifacts and metadata.

Artifactory and Nexus both allow searching by keywords, classes within artifacts, and GAV ( Group, Artifact, and version ) but in Artifactory its GAVC where can also be searched by a classifier.

Artifactory has various policy options to handle bad and missing checksums whereas Nexus involves specific permissions to restrict a repository browsing as well as searching through the web browser.

Auditing is much easier by using Artifactory, which involves an access log for the security-related incident. Especially logins, artifacts downloads, and deployments. This log can be viewed from the Artifactory UI and can be downloaded. Nexus logs don’t incorporate such detailed information, at least not in a separate way.

Nexus on the other side involves a special feature of RSS feeds for special events, such as for downloaded and deployed artifacts, logins, system configuration changes, and checksum errors. Artifactory doesn’t support RSS feeds.

Artifactory has no built-in special mechanism for removing artifacts after certain parameters e.g:- Lat use, path, tag, etc. whereas Sonatype Nexus has a built-in mechanism to support clearing up repositories.

To get trained and certification in both the tools there is a platform that is one of the best institutes DevOpsSchool. It claims to have the best and skillful trainers who hold a good experience, friendly environment, and practical projects that can help you guys to boost your carrier. So in my recommendation, if you are looking for an institute then it’s best in my consideration. Check once, guys.

Court Remands Kshitij Ravi Prasad to Judicial Custody

A special Narcotics Drugs and Psychotropic Substances (NDPS) Act court in Mumbai remanded Kshitij Ravi Prasad — a former executive producer at Dharmatic Entertainment — to judicial custody until October 6, 2020. Prasad had been arrested by the Narcotics Control Bureau (NCB) as part of its investigation into an alleged drug network linked to the death of Bollywood actor Sushant Singh Rajput.

Prasad was produced before the special NDPS court on Saturday following the expiry of his NCB custody period. Special public prosecutor Atul Sarpande confirmed the remand order.

NCB’s Allegations Against Prasad

The NCB told the court that Prasad had allegedly procured drugs from another accused individual named Karmjeet and his associates. The bureau had been questioning Prasad before formally placing him under arrest in connection with the broader Bollywood drugs probe.

Wider Context: Bollywood Drugs Investigation

The NCB’s investigation into an alleged drug network gained significant public attention following the death of actor Sushant Singh Rajput. Prior to Prasad’s remand, the agency had already arrested actor Rhea Chakraborty — who was Rajput’s girlfriend at the time of his death — along with her brother Showik Chakraborty and several other individuals in connection with the probe.

Separately, the Central Bureau of Investigation (CBI) was conducting its own investigation into the circumstances of Rajput’s death. Bihar Police had also booked the Chakrabortys under charges of abetment to suicide.

Defence Lawyer’s Claims

Prasad’s legal counsel, advocate Satish Maneshinde, alleged before the court that his client had been harassed and blackmailed by NCB officials into making a statement against filmmaker Karan Johar. The NCB did not publicly respond to these specific allegations at the time of the report.

This article is based on a news report originally published by New Indian Express in October 2020 and reflects the state of legal proceedings at that time.

The Case for Automating Dependency Security

Modern software development depends heavily on open source components. Every third-party library or framework added to a codebase introduces potential security risk, especially if that dependency is not kept up to date. As development organizations scale and try to ship faster, manually tracking and remediating vulnerable dependencies becomes impractical.

According to Sonatype’s 2019 State of the Software Supply Chain Report—which analyzed more than 36,000 open source components from the Maven Central Repository—exemplary development teams are significantly more likely to use automated tools to manage their open source software (OSS) dependencies. Those same teams also report a substantially lower rate of vulnerable component usage, demonstrating a clear correlation between automation and improved security posture.

Where Developers Work: Source Control Management Systems

Source control management (SCM) systems—such as GitHub, GitLab, and Atlassian Bitbucket—are central to modern development workflows. They are typically the first place where code is shared, reviewed by peers, and evaluated by automated tools. This makes SCMs a natural integration point for security and dependency management tooling.

Bringing security checks directly into the SCM layer means developers encounter policy violations and remediation guidance at the earliest possible moment—before vulnerable code is merged into a main branch or deployed to production.

The Problem with Existing Automated Dependency Solutions

A growing number of tools can automatically open pull requests to upgrade vulnerable dependencies. However, many teams report quickly disabling these integrations. The most common complaints include:

• Alert noise: Tools that generate large volumes of pull requests or notifications overwhelm developers and lead to “alert fatigue,” making it harder to prioritize genuine risks.
• Lack of policy context: Generic tools typically suggest upgrading to the next non-vulnerable version without considering whether that version aligns with an organization’s approved open source policies.
• False positives: Without precise vulnerability intelligence, tools may flag components that do not actually pose a risk in the context of how they are used.
• Haphazard updates: Blindly upgrading dependencies to the latest version can introduce breaking changes or compatibility issues without any guarantee of meaningful security improvement.

Sonatype Nexus Lifecycle and Automated Pull Requests for Bitbucket

Sonatype’s Nexus Lifecycle integrates with several SCM platforms, including Atlassian Bitbucket. The Bitbucket integration supports automated pull requests that are designed to address the shortcomings described above. Key characteristics of this approach include:

• Policy-aware remediation: Rather than suggesting the next available non-vulnerable version, Nexus Lifecycle evaluates candidate upgrades against your organization’s configured open source policies before recommending a fix.
• Nexus Intelligence data: Remediation guidance is backed by Sonatype’s proprietary vulnerability and component intelligence database, which is intended to reduce false positives compared to community-sourced vulnerability feeds alone.
• Reduced noise: By filtering recommendations through policy rules and accurate component data, the integration aims to surface only actionable pull requests—minimizing the volume of irrelevant alerts developers need to process.
• Automated dependency maintenance: Pull requests are opened automatically when a violation is detected, lowering the manual burden on developers and security teams.

How Policy-Driven Automation Differs from Generic Upgrades

A standard automated dependency tool might detect that lodash 4.17.4 has a known vulnerability and immediately open a pull request to upgrade to lodash 4.17.21. A policy-driven tool like Nexus Lifecycle performs additional checks:

• Is the proposed upgrade version itself on the organization’s approved list?
• Does the new version introduce any new policy violations (e.g., license incompatibilities)?
• Is the vulnerability actually exploitable given how the component is used in this project?
• Does the organization’s policy require upgrading, or is a workaround acceptable?

This additional context is what separates policy-driven automation from simple version bumping, and it is the primary reason teams are less likely to disable such integrations due to noise.

Getting Started: Integrating Nexus Lifecycle with Bitbucket

To take advantage of automated pull requests for Bitbucket with Nexus Lifecycle, your team will generally need:

1. An active Sonatype Nexus Lifecycle license with SCM integration enabled.
2. Atlassian Bitbucket (Cloud or Data Center—confirm which editions are supported with Sonatype directly).
3. An open source policy configured in Nexus Lifecycle that reflects your organization’s risk tolerance, approved licenses, and component standards.
4. Repository-level configuration to connect Bitbucket repositories to Nexus Lifecycle scans.

Once configured, Nexus Lifecycle monitors repositories for policy violations and opens targeted pull requests with remediation details, including the recommended upgrade version and the policy rationale behind the recommendation.

Key Takeaways

• Automating open source dependency management at the SCM layer is an increasingly common practice among high-performing development teams.
• Generic automated upgrade tools often create more problems than they solve due to noise and lack of policy context.
• Policy-driven tools like Sonatype Nexus Lifecycle aim to generate only actionable, context-aware pull requests in Atlassian Bitbucket.
• Integrating security into the developer workflow—rather than treating it as a downstream gate—reduces the cost and friction of remediating vulnerabilities.

For more information on Sonatype’s SCM integrations and open source policy management, visit the Sonatype product page.

Overview

How far off is Nexus AG (ETR:NXU) from its intrinsic value? Using financial data available in August 2019, this analysis examines whether the stock was fairly priced by forecasting future free cash flows and discounting them back to present value using the Discounted Cash Flow (DCF) method.

A DCF is just one valuation metric among many and is not without flaws. It works on the principle that a company’s value equals the present value of all cash it will generate in the future. The math is more approachable than the jargon suggests.

Is Nexus AG Fairly Valued?

This analysis uses a 2-stage DCF model:

• Stage 1: A 10-year explicit forecast of free cash flows, using analyst estimates where available and extrapolated figures otherwise.
• Stage 2: A terminal value representing the business’s cash flows beyond the forecast period, grown at a conservative rate tied to long-run GDP/bond rate assumptions.

Companies with shrinking free cash flow are assumed to slow their rate of shrinkage over time, and companies with growing free cash flow are assumed to see growth rates decelerate — reflecting the empirical tendency for growth to moderate in earlier years more than in later years.

10-Year Free Cash Flow (FCF) Forecast

The table below shows the levered FCF projections, the source of the growth rate estimate for each year, and the present value of each cash flow discounted at 6.56%.

(“Est” = FCF growth rate estimated by Simply Wall St)

Present Value of 10-year Cash Flow (PVCF) = €155.8m

Terminal Value Calculation

The second stage is the Terminal Value — representing the business’s cash flows after the explicit 10-year forecast period. A conservative long-run growth rate is used, capped at (and in this case set to) the 10-year German government bond rate of 0.2%. The cost of equity used is 6.6%.

Terminal Value (TV) = FCF₂₀₂₉ × (1 + g) ÷ (r − g) = €22m × (1 + 0.2%) ÷ (6.6% − 0.2%) = €345m

Present Value of Terminal Value (PVTV) = TV ÷ (1 + r)¹⁰ = €345m ÷ (1 + 6.6%)¹⁰ = €182.45m

Intrinsic Value per Share

The total equity value equals the sum of the 10-year present cash flows and the discounted terminal value:

Total Equity Value = €155.8m + €182.45m = €338.26m

Dividing by shares outstanding yields an intrinsic value estimate of approximately €21.53 per share. Against the share price of €28.10 at the time of writing (August 2019), the stock appeared potentially overvalued — trading at a roughly 30% premium to the DCF-derived fair value estimate.

As with any DCF model, remember: garbage in, garbage out. The output is only as reliable as the inputs.

Important Assumptions and Model Limitations

The two most critical inputs to any DCF are the discount rate and the projected cash flows. Changing either meaningfully will shift the intrinsic value estimate significantly. Key assumptions used here:

• Cost of equity: 6.6% — used as the discount rate because we are evaluating Nexus from an equity investor’s perspective, not using WACC (which would account for debt).
• Levered beta: 1.063 — derived from the industry average beta of globally comparable companies, constrained to a range of 0.8–2.0 to reflect a stable business.
• Terminal growth rate: 0.2% — based on the 10-year German government bond rate at the time, a deliberately conservative assumption.

The DCF model does not account for:

• Industry cyclicality
• Future capital requirements or financing needs
• Qualitative factors such as management quality, competitive moat, or regulatory environment

If you disagree with the assumptions, running your own sensitivity analysis — varying the discount rate by ±1–2% or adjusting terminal growth — is a useful exercise to understand how robust (or fragile) the valuation is.

Next Steps: Beyond the DCF

A DCF result should be a starting point for deeper research, not a final verdict. For Nexus AG, three additional areas are worth examining:

1. Financial Health: Does NXU carry a healthy balance sheet? Key checks include leverage ratios, interest coverage, and liquidity metrics.
2. Future Earnings Growth: How does NXU’s projected growth compare to healthcare technology peers and the broader market? Analyst consensus estimates for upcoming years provide useful context.
3. Relative Opportunities: Are there other high-quality companies in the sector that may offer a better margin of safety at current prices?

This analysis is based on data available as of August 27, 2019, sourced from Simply Wall St. It is provided for educational purposes to illustrate how a 2-stage DCF model works. It does not constitute current investment advice. Always conduct your own due diligence before making investment decisions.

What Is the Mass Index?

The Mass Index is a technical indicator developed by Donald Dorsey in the early 1990s. Its core purpose is to detect potential trend reversals by tracking the widening and subsequent narrowing of the high-low price range over a rolling period — typically 25 days.

The underlying logic is straightforward: when a price range expands significantly and then begins to contract, the market may be setting up for a directional shift. Dorsey identified a reading above 27 as the key threshold — sometimes called the “reversal bulge.” Once the index climbs above 27 and then falls back below 26.5, a reversal signal is generated.

What the Mass Index Does Not Tell You

A critical point that traders sometimes miss: the Mass Index signals that a reversal may be coming, but it says nothing about direction. A rising Mass Index reading means volatility is increasing — the trading range is widening. It does not indicate whether the stock will reverse upward or downward. Traders typically combine the Mass Index with a trend-following indicator (such as a simple moving average) to determine the likely direction of any reversal.

Williams %R: Measuring Overbought and Oversold Conditions

The Williams Percent Range (Williams %R) is a momentum oscillator developed by Larry Williams. It measures where the current closing price sits relative to the high-low range over a specified lookback period — most commonly 14 days.

The scale runs from 0 to -100:

• Above -20: The stock may be considered overbought — price is near the top of its recent range.
• Below -80: The stock may be considered oversold — price is near the bottom of its recent range.
• Between -20 and -80: Neutral territory; no strong overbought or oversold signal.

In the example case, a 14-day Williams %R reading of -33.98 places the stock in neutral territory, closer to the overbought threshold than the oversold threshold — suggesting modest bullish momentum at the time of the reading.

Average Directional Index (ADX): Gauging Trend Strength

The Average Directional Index (ADX), developed by J. Welles Wilder, measures the strength of a trend rather than its direction. It is derived from the moving average of price range expansion over a given period, commonly 14 days. The ADX line oscillates between 0 and 100.

Standard interpretation guidelines:

• 0–25: Weak or absent trend — the market may be ranging.
• 25–50: Strong trend in place.
• 50–75: Very strong trend.
• 75–100: Extremely strong trend — rare in practice.

The example reading of 14-day ADX at 19.13 falls in the 0–25 range, indicating a weak or consolidating trend at the time of measurement. This context is important: a Mass Index reversal signal during a weak-trend environment carries different implications than one occurring during a strong trend.

Commodity Channel Index (CCI): Spotting Emerging Trends and Extremes

The Commodity Channel Index (CCI), developed by Donald Lambert, measures the current price relative to its statistical average over a specified period. Despite the name, CCI is widely applied to equities and other asset classes.

Key interpretation levels:

• Above +100: Price is significantly above its average — potential overbought signal or the start of a strong uptrend.
• Below -100: Price is significantly below its average — potential oversold signal or the start of a strong downtrend.
• Between -100 and +100: Price is within a normal range relative to its recent average.

The example 14-day CCI reading of 30.83 sits well within neutral territory, consistent with the weak ADX reading and suggesting no extreme price displacement at the time.

Moving Averages: Identifying Support, Resistance, and Trend Direction

Moving averages are among the most widely used tools in technical analysis. They smooth out price data by calculating the average closing price over a defined number of periods, making it easier to identify the underlying trend direction.

Common moving averages and their typical uses:

• 50-day MA: Medium-term trend reference; frequently used to identify support in uptrends.
• 200-day MA: Long-term trend reference; widely watched by institutional traders as a bull/bear dividing line.

Moving averages are lagging indicators — they reflect past price action rather than predicting future moves. Their value lies in confirming trend direction and identifying dynamic support and resistance zones. A 200-day MA reading of 0.01 (as cited in the example) indicates the stock was trading at extremely low price levels, which is an important broader context when interpreting all other indicators.

Relative Strength Index (RSI): Momentum and Divergence

The Relative Strength Index (RSI), also developed by J. Welles Wilder, is a momentum oscillator that measures the speed and magnitude of recent price changes. It oscillates between 0 and 100.

Standard thresholds:

• Above 70: Potentially overbought.
• Below 30: Potentially oversold.
• Between 30 and 70: Neutral momentum.

RSI is also used to identify divergences — situations where price makes a new high or low but RSI does not confirm it. These divergences can be early warnings of trend exhaustion.

In the example, 14-day RSI at 57.97, 7-day at 58.24, and 3-day at 57.45 all cluster in neutral-to-mildly-bullish territory. The consistency across timeframes suggests stable, unexceptional momentum — no overbought or oversold extreme, and no meaningful divergence between short and longer periods.

Combining Indicators: Building a More Complete Picture

No single indicator tells the full story. Each of the tools described above answers a different question:

Experienced traders rarely rely on a single signal. A Mass Index reversal bulge combined with an RSI approaching overbought territory and a weakening ADX would be a more compelling case for caution than any one of those readings in isolation.

Risk Management: Knowing When to Exit a Losing Trade

Technical indicators help identify potential entry and exit points, but they are most valuable when paired with disciplined risk management. One of the most common — and costly — mistakes made by retail traders is the reluctance to close losing positions.

Behavioral finance research consistently shows that the psychological pain of realizing a loss feels more acute than the pleasure of an equivalent gain — a phenomenon known as loss aversion. This bias can cause traders to hold losing positions far longer than is rational, hoping for a recovery that may never come.

Practical approaches to managing this risk include:

• Pre-defined stop-loss levels: Set exit points before entering a trade, based on technical levels rather than emotion.
• Position sizing: Limit the size of any single position so that a full loss is tolerable within the overall portfolio context.
• Regular portfolio review: Periodically assess every open position against its original thesis — if the thesis is invalidated, the position should be reconsidered regardless of unrealized profit or loss.

Technical indicators such as those described in this article can serve as objective, rules-based triggers for these decisions — helping traders act on evidence rather than hope.

Summary

The Mass Index, Williams %R, ADX, CCI, moving averages, and RSI each illuminate a different dimension of market behavior — volatility, momentum, trend strength, and mean reversion. Used together and interpreted in context, they form a more reliable basis for trading decisions than any single signal. The specific readings discussed here (sourced from August 2019 data) are illustrative only; always apply these tools to current data and in the context of your own risk tolerance and investment objectives.

A People-First Philosophy Drives Award-Winning Firm

On Kenner Kingston’s desk at Salt Lake City-based Architectural Nexus sit schematic sketches that tell the story of the firm’s evolving mission. They are not renderings for a hospital wing or a research laboratory—two market segments where Architectural Nexus has built considerable expertise—but rather plans for a rainwater collection and reuse system for an off-the-grid home in Moab, Utah. The firm is collaborating with a community nonprofit that helps low-income residents construct their own sustainable straw-bale homes in the desert region.

That project encapsulates what Kingston, president of Architectural Nexus, describes as a fundamental shift in the firm’s thinking over the past five years.

“In the past five or so years, we’ve had a real shift in our thinking. It is not about the project or the building, it is about the people. We are people driven in the pursuit of meaningful experiences.”

— Kenner Kingston, President, Architectural Nexus

That philosophy earned Architectural Nexus recognition as ENR’s 2019 Intermountain Design Firm of the Year. The firm was founded through the 2003 merger of Jensen Haslem Architects and Thomas Petersen Hammond Architects, and has since grown to nearly 120 employees with offices in Salt Lake City and Sacramento, California. The firm reported revenue of $19.9 million in 2017 and $22 million in 2018, regularly ranking among the top ten design firms in the Intermountain region.

A Diverse and Multidisciplinary Design Studio

Robb Harrop, director of design at Architectural Nexus, articulates the firm’s client-centered approach succinctly: “We like projects that have a purpose and a vision. Something deeper than just keeping the rain off your head. We want to help clients find what is meaningful to them.”

That approach has produced strong results across multiple sectors. In healthcare, the firm has designed all four completed phases of the Huntsman Cancer Institute (HCI) at the University of Utah in Salt Lake City. The most recent phase—a 230,000-square-foot, $100-million research and office facility—exemplifies the firm’s patient-centered design thinking. Ben Tanner, executive director of the HCI, credits Architectural Nexus with understanding the unique needs of oncology patients.

“Their thoughtful work shows up in our patient satisfaction surveys. Patients always have great things to say about the look and feel of our buildings, and it’s a wonderful place for our clinical and research staff as well.”

— Ben Tanner, Executive Director, Huntsman Cancer Institute

A fifth phase of the HCI project was underway at the time of the award. The firm also completed a $114-million hospital in Nampa, Idaho, for the St. Luke’s Health System, which opened in fall 2017. Sandee Gehrke, vice president of operations at St. Luke’s, praised Architectural Nexus for investing time to understand the organization’s culture and brand identity before putting pen to paper.

Beyond healthcare, the firm’s Salt Lake City portfolio includes the $160-million, 400,000-square-foot Hardware Village apartment and condominium complex and a $7-million, 48,000-square-foot mixed-use residential and retail building in the city’s 9th and 9th district. In higher education, the firm completed the College Activities Center at Gillette College in Gillette, Wyoming, which features a 2,100-seat basketball arena, athlete support facilities, and flexible multi-use space.

Multiple LEED-certified designers work alongside specialists in landscape design, energy analysis, interior design, animation and visualization, and graphic design. Kingston notes that housing all these disciplines under one roof enables the firm to pursue both large, complex commissions and smaller experimental projects that push the boundaries of new technology and construction techniques.

Employee Ownership as a Cultural Cornerstone

Architectural Nexus was in the process of completing an Employee Stock Ownership Plan (ESOP) in 2019. For Kingston, what began as a leadership-transition and financial planning tool evolved into a genuine expression of the firm’s values.

“In 2014 we really had a change in mindset, and the ESOP went from being a financial tool to a culture tool, a way to align with the values of the firm… One of our partners said at one point, ‘What is more Nexus than an ESOP?’ and it just hit me that he was right.”

— Kenner Kingston, President, Architectural Nexus

Julie Berreth, vice president of operations, describes the firm’s internal culture as deliberately flat—characterized by a compressed compensation structure, a commitment to paying employees a living wage, and an extensive mentoring program designed to develop the next generation of architects and designers. The firm also joined the International Living Future Institute’s (ILFI) JUST program, which provides guidelines and external auditing on social justice and diversity performance.

To translate these values into direct community impact, Architectural Nexus launched the Nexus Builds program approximately two years prior to receiving the award. The initiative has partnered with the Seattle-based Block program to design and build tiny off-the-grid homes for people experiencing homelessness on donated urban lots. At the time of the award, employees were constructing a tiny home in a corner of the firm’s Salt Lake City headquarters parking lot, scheduled for delivery to Seattle. Director of communications Brian Cassil described the project as meaningful beyond simple volunteerism: “This is very purpose driven, but at its core it is also about mastery and how to get better at what we do.”

Beyond Conservation: Embracing Regenerative Design

Architectural Nexus has been an early advocate of sustainable design in the Intermountain region. In 2010, its Salt Lake City office became one of the first LEED Platinum certified buildings in the area. But the firm’s ambitions have since moved well beyond conventional green building metrics.

The clearest expression of this trajectory is the firm’s Sacramento office, a renovated office and warehouse building that opened in 2016 in the city’s historic district. The project was designed in accordance with the International Living Future Institute’s Living Building Challenge (LBC)—one of the most rigorous sustainability frameworks in the built environment industry. The completed building features a composting system, onsite agriculture, onsite water filtration and treatment, highly efficient electrical systems, and a solar photovoltaic array. It achieved LEED Platinum certification (level four) and was recognized in 2018 as the first Living Building in California and the 19th in the world certified by ILFI.

Berreth frames the firm’s design philosophy as anticipatory rather than reactive: “We don’t want to look at a building stuck on a site, but how it enhances the wider community and the people around it. Even if we are not putting something like PV panels on a project today, we want to anticipate they might be added one day and design space for them.”

Kingston sees regenerative design—which seeks to restore the built environment to a more natural state, treating buildings as habitats rather than machines—as the logical next phase for the industry and the firm’s greatest strategic opportunity.

“For a long time, most firms in our industry have been climbing this mountain called sustainability. Some of us who were lucky got to the top and looked across to see what was next, and we saw regenerative design, things like the Living Building Challenge… I’m excited for the next five years because I think we are perfectly positioned for oncoming growth in regenerative design.”

— Kenner Kingston, President, Architectural Nexus

From rainwater systems for low-income desert housing to one of California’s most advanced Living Buildings, Architectural Nexus continues to demonstrate that people-centered architecture and environmental responsibility are not competing priorities—they are the same goal expressed at different scales.

Nexus Repository Wins Best Open Source DevOps Tool

Sonatype announced in March 2018 that its Nexus Repository Manager had been named Best Open Source DevOps Tool by Computing magazine at the DevOps Excellence Awards 2018. The award was presented on 21 March 2018 at a gala ceremony in London, where Computing recognised outstanding achievements from organisations, individuals, and solutions operating within the DevOps space.

Wayne Jackson, CEO of Sonatype, commented on the award:

“Nexus Repository has become a de facto standard within DevOps toolchains worldwide and is simply the best way to continuously control binaries and build artifacts as they flow through the modern SDLC. We’re honoured that Computing and the DevOps Excellence Award judges saw the value, and importance, in what we’ve built with Nexus Repository. This award further validates the choice that 10 million developers have made to use Nexus as their system of record for open source components, build artifacts, and release candidates.”

— Wayne Jackson, CEO, Sonatype

What Is Nexus Repository?

Nexus Repository Manager is a universal artifact repository that helps development teams store, organise, and distribute software components — from raw source dependencies through to release candidates and final binaries. It acts as a single source of truth for all build artifacts within the software development lifecycle (SDLC), enabling teams to enforce quality gates, security policies, and license compliance at the point where components enter the pipeline.

A key differentiator at the time of the award was its broad format support. Nexus Repository offered free support for all major package formats, including:

• Java (Maven, Gradle)
• JavaScript (npm)
• Python (PyPI)
• Ruby (RubyGems)
• .NET (NuGet)
• Docker container images
• Git LFS (large file storage)

Key Stats Cited at the Time of the Award (March 2018)

The following figures were reported by Sonatype as part of the award announcement and reflect the state of the Nexus ecosystem in early 2018:

• 10 million active users across approximately 150,000 software development organisations
• 115,000 repositories scanned daily for open source security vulnerabilities
• 44 free community-built integrations
• 100+ free online training videos
• 50 DevOps reference architectures featuring Nexus

DevOps Toolchain Integrations

Part of Nexus Repository’s appeal to DevOps teams is its out-of-the-box compatibility with a wide range of established tools. At the time of the award, documented integrations included:

• CI/CD: Jenkins, Bamboo
• IDEs: Eclipse, IntelliJ IDEA
• Containers & orchestration: Docker, OpenShift, Mesosphere
• Configuration management: Puppet, Chef
• Issue tracking & quality: JIRA, SonarQube

This breadth of integration means Nexus can be inserted into an existing toolchain without requiring teams to replace other components — a practical advantage when evaluating repository managers for enterprise adoption.

About Sonatype

Sonatype is best known as the organisation behind several foundational open source infrastructure projects: Apache Maven, the Maven Central Repository, and Nexus Repository. The company positions itself at the intersection of open source consumption and security governance — helping engineering teams benefit from the vast open source ecosystem while managing the associated supply chain risks.

As of the 2018 announcement, Sonatype was privately held, with investment from New Enterprise Associates (NEA), Accel Partners, Hummer Winblad Venture Partners, and Goldman Sachs.

Why This Recognition Matters for DevOps Teams

An artifact repository manager is often an unglamorous but critical piece of DevOps infrastructure. Without a well-governed repository, teams face problems such as:

• Uncontrolled ingestion of third-party dependencies with unknown vulnerabilities
• Build reproducibility failures when upstream packages change or disappear
• Difficulty enforcing licence compliance across large codebases
• Slow build pipelines caused by repeated internet fetches of identical artifacts

Nexus Repository addresses all of these concerns by acting as a proxy, cache, and governance layer between developers and the open source ecosystem. Winning the Computing DevOps Excellence Award in this category reflected its widespread adoption and the practical value it delivers inside real-world SDLC pipelines.

Note: Statistics and product capabilities described in this article reflect the state of Nexus Repository as of March 2018. Current figures and supported formats may differ. Consult sonatype.com for up-to-date information.