EYMINT
DocumentationAPI Reference
BlogDashboard
EYMINT
SectionsDocumentationAPI Reference

Getting Started

  • Keymint Documentation
  • Introduction
  • Getting Started
  • License Keys
  • Changelog

SDK References

  • Software Development Kits (SDKs)
  • Node.js SDK
  • Go SDK
  • Python SDK
  • C# SDK

Integration Guides

  • Integration Guides
  • Customer Portal for Vendors
  • Roles & Permissions
  • Radar Alert Destinations
  • Payment Provider Integrations
  • Stripe Subscription Licensing
  • Email Delivery
  • API Key Management
  • Webhook Deliveries
  • Analytics and Retention
  • Dashboard Workflows
  • Electron Licensing
  • PyQt Licensing
  • Tauri Licensing
  • Next.js SaaS Licensing

Licensing Guides

  • Licensing Concepts
  • Node-Locking & Machine Identifiers
  • Floating Licenses
  • Offline Verification
  • License Radar
  • Public Key Management and Rotation
  • Feature Flags
  • Webhooks & Events

Templates

  • Starter Templates
  • Electron License Starter
  • PyQt License Starter
  • Tauri License Starter
  • Next.js SaaS License Starter

Security & Trust

  • Security & Trust

Support

  • Frequently Asked Questions
  • Customer Portal
  • Using the Customer Portal
  • Workspace Settings and Roles

Legal

  • Privacy Policy
  • Subprocessors
  • Data Processing Agreement
  • Security Overview
  • Terms of Service
  • Service Level Agreement (SLA)
  • GDPR Compliance
Go to Dashboard

Getting Started

  • Keymint Documentation
  • Introduction
  • Getting Started
  • License Keys
  • Changelog

SDK References

  • Software Development Kits (SDKs)
  • Node.js SDK
  • Go SDK
  • Python SDK
  • C# SDK

Integration Guides

  • Integration Guides
  • Customer Portal for Vendors
  • Roles & Permissions
  • Radar Alert Destinations
  • Payment Provider Integrations
  • Stripe Subscription Licensing
  • Email Delivery
  • API Key Management
  • Webhook Deliveries
  • Analytics and Retention
  • Dashboard Workflows
  • Electron Licensing
  • PyQt Licensing
  • Tauri Licensing
  • Next.js SaaS Licensing

Licensing Guides

  • Licensing Concepts
  • Node-Locking & Machine Identifiers
  • Floating Licenses
  • Offline Verification
  • License Radar
  • Public Key Management and Rotation
  • Feature Flags
  • Webhooks & Events

Templates

  • Starter Templates
  • Electron License Starter
  • PyQt License Starter
  • Tauri License Starter
  • Next.js SaaS License Starter

Security & Trust

  • Security & Trust

Support

  • Frequently Asked Questions
  • Customer Portal
  • Using the Customer Portal
  • Workspace Settings and Roles

Legal

  • Privacy Policy
  • Subprocessors
  • Data Processing Agreement
  • Security Overview
  • Terms of Service
  • Service Level Agreement (SLA)
  • GDPR Compliance

Service Level Agreement (SLA)

Keymint's current service availability, support targets, and how we approach uptime commitments today.

Keymint currently provides the service on a best-effort availability basis. We do not currently offer a contractual monthly uptime percentage, uptime service credits, or guaranteed recovery time and recovery point objectives.

We are improving the service's redundancy, monitoring, and disaster-recovery controls. Numerical commitments will only be published after those controls have been implemented and tested.

Support Targets

We prioritize issues based on severity and subscription tier. The response times below are operational targets, not guaranteed service levels.

Issue SeverityFree TierMaker TierStartup TierStandard Tier
Severity 1 (Critical outage)Best EffortWithin 12 business hoursWithin 12 business hoursWithin 4 hours
Severity 2 (High impact)Best EffortWithin 24 business hoursWithin 24 business hoursWithin 12 hours
Severity 3 (General queries)Best EffortWithin 2 business daysWithin 2 business daysWithin 1 business day

Maintenance & Incident Policies

  • Scheduled Maintenance: We perform scheduled maintenance during low-traffic windows. We provide at least 48 hours email notice for any scheduled updates that could cause service disruption.
  • Incident Management: We investigate service interruptions and communicate material incidents through available customer-support channels.
  • Backup & Disaster Recovery: Database backup and recovery capabilities depend on the active managed-database plan. Recovery procedures and achievable recovery times remain under verification and are not currently guaranteed.

Availability Limitations

Service availability can be affected by customer code errors, force majeure events, third-party network or provider failures, and customer-induced security incidents.

On this page

  • Support Targets
  • Maintenance & Incident Policies
  • Availability Limitations