Book a demo

01 // SOLUTIONS BY DELIVERY MODEL

One platform. Three ways to deploy it across your enterprise.

Locus is not a take-it-or-leave-it application. It is a platform that your organization can operate at whatever level of depth and independence your IT capacity, internal expertise, and operational complexity require — from self-service configuration to fully engineered, consultant-delivered solutions. All three delivery models run on the same governed, multitenant, SOC 2 Type 2-verified infrastructure.

Delivery Model 1: Application Configuration →
Delivery Model 2: App Builder →
Delivery Model 3: Custom App Delivery →

Talk to a Solutions Architect
Young EHS and ESG professionals working on AI and environmental data

02 // WHY THIS MATTERS TO TECHNOLOGY LEADERS

Professional working on laptop beside servers

Fewer vendors. More capability. A platform your organization can grow into.

Enterprise technology leaders managing EHS and sustainability programs face a common pressure: the number of point solutions — each with its own vendor relationship, data silo, integration burden, and security review cycle — keeps growing as regulatory obligations expand. The Locus delivery model addresses that directly.

Every application your organization deploys through Locus, regardless of which delivery model produced it, runs on a single multitenant platform with a shared data model, shared security controls, and a single integration surface. Your IT evaluates Locus once. Legal reviews one agreement. Security assesses one architecture. Your organization then deploys as many applications as it needs — configured by your power users, built by your analysts, or engineered by Locus consultants — without re-entering that procurement and validation cycle for each one.

For procurement leaders, this means a single vendor relationship covers the full spectrum from off-the-shelf EHS&S apps to purpose-built enterprise applications. For CIOs and CISOs, it means every new EHS and sustainability application your organization adds inherits the same security protocols, SOC 1 and SOC 2 Type 2 verification, AWS hosting, and 99.99%+ uptime record that your initial Locus deployment established.

Delivery Model 1: App Configuration

Your team shapes the software to fit the work.
The starting point for most Locus customers is a library of 30+ purpose-built EHS and sustainability applications, each ready for use and each configurable without writing a line of code. App Configuration puts ongoing control entirely in the hands of your organization — specifically, your power users with environmental, safety, or sustainability domain knowledge.

Configuration happens inside the Locus Configuration Workbench, which is a browser-based, drag-and-drop environment that governs how existing Locus apps behave for your organization. Power users adjust field labels, add new data inputs, define conditional logic, build multi-step approval workflows, assemble dashboards, and produce regulatory report templates, all without IT involvement and without submitting a change request to Locus.

What IT and procurement leaders need to know
Every configuration change made by a power user is stored as metadata within your tenant rather than being hard-coded. This architecture has two significant consequences. First, configurations are preserved through every Locus Platform update; your organization's forms, logic, and reports are never overwritten by a new release. Second, configuration changes never alter the underlying platform codebase, which means they carry no security or stability risk to the shared infrastructure. Your IT team retains full governance over the platform while EHS&S operators retain full control over how their applications behave.

The operational cost is also key: configuration changes made by your team cost nothing beyond the subscription. There are no vendor professional services fees, no change order processes, and no release schedules to wait for. When a regulation changes and a report format needs updating, your team updates it. When a new facility opens and its specific monitoring parameters need to be captured in a form, your team adds them.

For organizations with strong internal EHS or sustainability teams and a preference for maximum operational independence, App Configuration is the most efficient path to a fully adapted platform.

Who this model fits
App Configuration is the right delivery model for organizations with experienced EHS, sustainability, or environmental data management professionals who want full day-to-day control over how their software behaves — and who want to make changes on their own schedule without depending on a vendor queue.

Well suited for: Multi-site industrial organizations with standardized EHS programs, water utilities managing permit compliance across a defined service territory, sustainability teams managing ESG disclosure frameworks with evolving data requirements, and any organization where the EHS team has the bandwidth and technical confidence to own platform operations.

Learn more about Locus Configurability →

AI and computer engineering reviewing environmental data and AI models

Delivery Model 2: App Builder

Your team builds new applications without writing code.
The Configuration Workbench is not limited to modifying existing Locus apps. It is also a full no-code development environment that your team can use to build entirely new applications from scratch on the Locus Platform. The App Builder delivery model extends the scope of what Locus can do for your organization well beyond the 30+ applications in the standard library.

This model is built around a concept Locus calls the user-developer: a business or operational expert who can translate real-world processes into configurable digital applications without being a traditional software programmer.

In Locus, this means someone who knows how to lay out information clearly, draw a workflow or flow chart, and build structured logic similar to a spreadsheet using formulae, sorting, tables, and charts. An analyst or operations manager who understands a compliance workflow, a data collection process, or an internal reporting requirement not already covered by a pre-built Locus app can design something new in the Configuration Workbench. They define the form fields, specify the calculation logic, configure the workflow routing, set up the dashboard visualization, and deploy the app to end users — all without involving a developer, submitting a procurement request, or engaging an external vendor.

By empowering user-developers, organizations can adapt applications faster, respond to changing regulations or business needs, and maintain consistent, governed, auditable systems without waiting for custom software development.

What IT and procurement leaders need to know
The App Builder model has meaningful architectural implications for enterprise IT strategy. Every application built by your team in the Configuration Workbench runs on Locus Platform infrastructure, which means it inherits the platform's SOC 2 Type 2 verification, multitenant data isolation, AWS hosting, role-based access controls, SSO integration, and audit trail architecture automatically. Your team builds the application logic; Locus Platform supplies the security, the data governance, and the operational infrastructure.

For organizations that have historically used spreadsheets, Access databases, or SharePoint lists to manage specialized compliance or operational data, the App Builder delivery model offers a governed, auditable, mobile-enabled alternative on infrastructure that already meets your enterprise security standards. The application your EHS analyst builds in the Configuration Workbench on a Tuesday afternoon is production-ready, audit-compliant, and available to field teams on mobile devices by end of week, with no IT involvement beyond the original platform onboarding.

From a vendor consolidation perspective, every net-new application your team builds on Locus Platform is an application that does not require a new vendor evaluation, a new security review, a new contract negotiation, or a new integration project. It runs in your existing Locus tenant, connects to your existing environmental data, and is governed by the same administrative controls your IT team already manages.

Who this model fits
App Builder is the right delivery model for organizations with operational or compliance processes that fall outside the scope of standard off-the-shelf applications, but whose internal teams have the bandwidth and domain knowledge to design and own the resulting application. The model works best where user-developers already exist in practice — EHS managers, sustainability analysts, compliance coordinators, and operations leads who think in workflows and structured data, even if they have never written a line of code.

Well suited for: Organizations replacing spreadsheet-driven compliance processes with governed, mobile-enabled applications; EHS or sustainability teams with specialized data collection or reporting requirements that are not covered by existing Locus apps; enterprise IT organizations looking to consolidate departmental compliance tools onto a single governed platform without building custom software from scratch; and organizations in sectors with highly specific regulatory or operational workflows such as oil and gas, government, large-scale construction, or complex water utilities.

Explore the Locus ecosystem →

Delivery Model 3: Custom App Delivery

Locus Technologies engineers a solution to your specification.
Some compliance programs, data environments, or operational requirements are too complex, too sensitive, or too technically demanding for self-service delivery. Custom App Delivery is the engagement model where Locus consultants — environmental scientists and software engineers with direct domain expertise — take on the design, development, and delivery of a purpose-built solution engineered to your organization's specific requirements.

This is not a generic professional services offering. The Locus team that delivers a custom application holds the same credentials as the team that built the platform: advanced degrees in environmental science, chemistry, civil engineering, and related disciplines, alongside software architecture experience from organizations including Hewlett-Packard, PeopleSoft, and Salesforce.

When a Locus consultant is scoping a custom waste tracking application for a multi-billion-dollar remediation program or a specialized produced water management system for an oil and gas operator, they understand both the regulatory obligation being addressed and the engineering challenge being solved.

What IT and procurement leaders need to know
Custom App Delivery is a managed engagement with defined scope, documented configuration, and a clear handoff process. The deliverable is a production application running on Locus Platform and subject to all the same governance, security, and operational standards as every other application in your tenant. After delivery, your organization owns and operates the application. Your team can make ongoing adjustments through the Configuration Workbench. Locus Support covers the application exactly as it covers all platform applications.

This matters because it changes the risk profile of enterprise software development considerably. A custom application delivered by Locus does not create a shadow IT asset or a bespoke codebase that requires its own maintenance cycle, security review, and upgrade path. It is a configured application on a continuously updated, externally audited, enterprise-grade platform. The technical debt that typically accumulates around custom enterprise software development does not accumulate here.

For procurement leaders and CIOs managing a portfolio of point solutions, Custom App Delivery offers an alternative: rather than engaging a systems integrator to build something new on yet another platform, your organization works with a single vendor — whose platform you already trust and whose team already understands your compliance environment — to extend that platform's capability into new problem spaces.

Locus maintains relationships with software specialty firms for additional implementation capacity where project scope warrants it, giving enterprise customers access to expanded delivery resources without leaving the Locus ecosystem.

Who this model fits
Custom App Delivery is the right model for programs where the complexity, regulatory sensitivity, data volume, or integration requirements exceed what an internal team can effectively scope and build independently — or where the stakes of getting it wrong are high enough that managed delivery by domain experts is the lower-risk path.

Well suited for: Multi-agency government programs with specialized data management requirements, remediation programs managing large volumes of historical environmental data across complex site networks, oil and gas or chemical operators with proprietary calculation methodologies that must be encoded precisely, organizations undergoing a major EHS&S platform consolidation that requires migrating and validating legacy data at scale, and any program where regulatory defensibility of the data architecture is a requirement, not just a preference.

Learn about Locus Implementation Services →

06 // Choosing the right model

The three delivery models are not mutually exclusive.

Many Locus customers use all three across different parts of their organization simultaneously — running standard apps in App Configuration mode for their core EHS compliance programs, using App Builder to address specialized operational needs, and engaging Custom App Delivery for a complex integration or data migration that benefits from Locus engineer involvement.

The choice of delivery model determines who builds the application and how. It does not change the platform those applications run on. Across all three delivery models, every Locus application operates within the same governed infrastructure.

07 // THE INVARIABLE FOUNDATION

What does not change, regardless of delivery model

Security and compliance posture
SOC 1 Type 2 and SOC 2 Type 2 verification of Locus's own operations and security controls, not merely the hosting provider's. AWS infrastructure. SSO support. Role-based access controls. Multitenancy. 99.99%+ uptime since 2009, verified by independent third-party monitoring and published publicly in real time.

Unified data model
Every application — whether configured from an existing Locus app, built from scratch in App Builder, or engineered by Locus consultants — shares the same underlying data model. Data entered or collected in one application is immediately available to every other application in the tenant. No integration work, no redundancy, no reconciliation.

Audit trail and data integrity
Every record carries a complete audit chain. Configuration changes are logged with timestamps and user attribution. Data transformations are documented. The audit infrastructure that makes Locus data defensible in a regulatory context is not a feature of specific applications; it is a property of the platform that every application inherits.

Platform updates without disruption
Locus updates the underlying platform continuously. Application configurations, whether made by your power users or by Locus consultants, are stored as metadata and are never overwritten by a platform release. The platform improves; your configurations remain.

08 // Talk with Us

Not sure which delivery model fits your organization's next project?

Talk to a Locus solutions architect. They will assess your program requirements, your internal resource capacity, and your IT governance needs — and recommend the delivery model, or combination of models, that makes the most sense.
Talk with a Solutions Architect

Common questions about Locus delivery models

09 // FAQ

Yes. Many Locus customers run standard applications in App Configuration mode alongside applications built through App Builder and, in some cases, solutions delivered by Locus consultants through Custom App Delivery — all within the same tenant. The delivery model is a per-application decision, not an organization-wide commitment.

App Builder is available to any Locus customer with platform access — no separate subscription is required. Custom App Delivery is a scoped professional services engagement that is priced and contracted separately, but the resulting application runs on your existing Locus platform subscription. Your organization does not pay for separate hosting, maintenance, or upgrade services for custom-delivered applications.

Nothing disruptive. Because all applications on Locus Platform — including those engineered by Locus consultants — are built as configurations on the metadata-driven architecture, they are preserved through platform updates. Your custom application does not require re-testing or re-deployment after a platform release.

Locus Platform includes role-based access controls that determine which users can access the Configuration Workbench and what they can modify within it. Administrative rights, configuration rights, and end-user rights are all separately governed. Your IT team defines the permission structure; Locus enforces it.

Because App Builder applications run on Locus Platform infrastructure — which your organization has already evaluated through its standard security and procurement processes — net-new applications built through App Builder do not require a separate security review. They inherit the platform's SOC 2 Type 2 verification, AWS hosting security controls, and data governance posture automatically.

Contact the Locus solutions team to initiate a scoping conversation. Locus assigns a dedicated implementation manager with domain expertise relevant to your program. The engagement follows a defined process: scoping, design, build, live configuration review, delivery, and handoff — with full documentation of the delivered configuration maintained in an accessible location.