LeadNest categorizes products and features into the following lifecycle stages.
Alpha
Alpha Services are early-stage features made available to a limited number of customers for evaluation and testing.
Characteristics of Alpha Services include:
- •Invitation-only access
- •Experimental functionality
- •Significant ongoing development
- •Limited documentation
- •APIs and user interfaces may change without notice
- •Limited or no migration support
- •Support provided primarily by engineering teams
Alpha Services are not intended for production use. LeadNest does not provide service level commitments or uptime guarantees for Alpha Services.
Beta
Beta Services are substantially more complete than Alpha Services but remain under active development.
Beta Services may include:
- •Stable core functionality
- •Expanded documentation
- •Support through the LeadNest Support Team
- •Ongoing feature enhancements
However, Beta Services may still experience:
- •Breaking API changes
- •Performance issues
- •User interface changes
- •Missing features
- •Compatibility limitations
Customers should evaluate Beta Services before deploying them in production environments. Unless otherwise specified, Beta Services are not covered by enterprise Service Level Agreements (SLAs).
General Availability (GA)
Generally Available ("GA") Services are fully released and intended for production use.
GA Services receive:
- •Full production support
- •Security updates
- •Bug fixes
- •Performance improvements
- •Product documentation
- •Ongoing maintenance
Unless otherwise specified in a separate agreement, GA Services are supported under LeadNest's standard support policies.
Long-Term Support (LTS)
Certain APIs, SDKs, enterprise modules, or platform components may be designated as Long-Term Support (LTS).
LTS Services receive:
- •Security updates
- •Critical bug fixes
- •Compatibility updates
- •Extended maintenance support
Feature enhancements during the LTS period may be limited.
Deprecated
A Service enters the Deprecated stage when LeadNest intends to replace or discontinue it.
During this period:
- •Existing functionality remains available.
- •New development should target supported alternatives.
- •Critical security fixes may continue.
- •Documentation remains available.
- •New feature development is generally discontinued.
LeadNest will make commercially reasonable efforts to notify affected Customers before retiring Deprecated Services. Except where immediate action is required for security, legal, operational, or third-party reasons, LeadNest generally intends to provide at least ninety (90) days' notice before permanently discontinuing a Deprecated Service.
Enterprise customers with active support agreements may request reasonable migration assistance during the deprecation period.
End-of-Life (EOL)
When a Service reaches End-of-Life (EOL):
- •The Service is no longer supported.
- •Security updates cease.
- •Bug fixes cease.
- •Technical support ends.
- •APIs may be disabled.
- •Integrations may stop functioning.
- •Documentation may be archived.
LeadNest may permanently remove End-of-Life Services from the Platform. In limited cases, LeadNest may continue to make certain SDKs, client libraries, or developer tools available through public repositories for community use. Such software is provided without maintenance, updates, warranties, or support.