High-Performance API Gateway for Microservices
Answers to common questions about routing, billing, data retention, and multi-region deployments.
General
Platform overview, account management, and core capabilities.
What is the default data retention period for API traffic logs?
FluxGate retains raw access logs for 30 days on all plans. Enterprise customers can extend retention to 365 days via the console or request immutable cold storage exports to AWS S3 or Azure Blob. Aggregated analytics metrics are stored indefinitely.
How does FluxGate handle rate limiting across multiple services?
Rate limiting is applied at the gateway edge using a distributed Redis-backed counter. You can configure limits per route, per API key, or per client IP. Burst allowances are adjustable, and exceeded requests receive a standard `429 Too Many Requests` response with `Retry-After` headers.
Billing & Pricing
Usage metrics, overage policies, and enterprise licensing.
What happens if I exceed my monthly request quota?
FluxGate does not throttle or drop traffic upon quota exhaustion. Instead, overages are billed at $0.0005 per additional request, capped at 200% of your plan's baseline. You can set hard limits or budget alerts in the Billing Dashboard to prevent unexpected charges.
Do you offer volume discounts for multi-year contracts?
Yes. Committing to a 24-month term unlocks a 22% discount on Pro and Enterprise tiers. Annual commitments receive a 12% reduction. Contact our sales team to configure reserved capacity or custom SLA pricing.
Technical & Deployment
Multi-region support, migration paths, and infrastructure configuration.
How does multi-region active-active routing work?
FluxGate uses GeoDNS and real-time health probes to route traffic to the nearest healthy region. If a primary region experiences latency spikes >150ms or fails health checks, traffic automatically fails over to a secondary region within 2 seconds. Session affinity and sticky cookies are preserved across regions using our distributed state store.
Can I migrate from Kong or Nginx without rewriting my routes?
Absolutely. Our `fg-migrate` CLI tool parses Kong YAML decK files and Nginx `conf.d` directories, translating upstream definitions, plugins, and rewrite rules into FluxGate's native JSON schema. The tool validates syntax, maps equivalent rate-limiting/transform plugins, and outputs a ready-to-deploy configuration. Typical migrations for 50+ routes take under 15 minutes.
What container orchestration platforms are supported?
FluxGate provides official Helm charts for Kubernetes, Terraform modules for AWS EKS/GKE, and native Docker Compose manifests. The control plane is cloud-agnostic, and the data plane runs as a lightweight sidecar or standalone daemon set. Custom OCI registries and air-gapped deployments are fully supported.
How do I configure mTLS between the gateway and downstream services?
Enable mutual TLS in the route configuration by uploading your CA certificate and client certificate bundle. FluxGate automatically rotates certificates before expiration and validates downstream service identities against your specified CN or SAN patterns. All mTLS handshakes are logged for audit compliance.
Still have questions?
Our engineering team monitors the community forum and responds within 4 hours during business days.