When you start using LexyFill, the first thing you’ll notice is that it comes with a handful of hard‑coded constraints that can shape your workflow. The most common limitations include file‑size caps, user‑seat restrictions, platform‑compatibility gaps, API throttling thresholds, data‑retention policies, and licensing boundaries. If you want a deeper look at the product, check out the official page for lexyfill.
Core Functional Limits
LexyFill is built around a few non‑negotiable technical ceilings that you’ll hit sooner or later:
- Maximum upload size: 2 GB per file on the Business tier; the Free plan caps at 200 MB.
- Concurrent user sessions:
- Free: 1 session
- Pro: up to 5 sessions
- Enterprise: up to 25 sessions (extra seats can be added at $15 per seat/month)
- Record limits per project: 10,000 records on Free; 250,000 on Pro; unlimited on Enterprise (subject to storage quota).
- Processing queue depth: 500 jobs in the queue; any jobs beyond this are queued for the next processing window, typically ≤5 minutes.
Compatibility & Integration Constraints
LexyFill’s native integrations are solid but not exhaustive. Here’s a quick reference:
| Category | Supported | Unsupported / Notes |
|---|---|---|
| Operating Systems | Windows 10+, macOS 10.14+, Ubuntu 18.04+, RHEL 8 | No native support for Windows 7, macOS 10.13, or older Linux distros |
| Mobile Platforms | iOS 13+ (app), Android 10+ (web‑based PWA) | No dedicated Android app; PWA requires Chrome 88+ |
| Cloud Storage | AWS S3, Google Cloud Storage, Azure Blob | OneDrive, Dropbox (no native connector; requires third‑party webhook) |
| Authentication | SAML 2.0, OAuth 2.0 (Google, Microsoft) | LDAP/Active Directory (Enterprise plan only) |
| API Rate Limits | 100 req/min on Pro; 500 req/min on Enterprise | Free tier: 20 req/min (burst to 30 for 5 seconds) |
Performance & Scalability Boundaries
LexyFill is fast for typical workloads, but its architecture imposes a few performance ceilings:
- Latency:
- US‑East (Virginia): ~120 ms average
- EU‑West (Ireland): ~210 ms
- Asia‑Pacific (Sydney): ~340 ms
- Throughput per node: 1,200 records/minute before throttling kicks in.
- Maximum cluster size: 3 nodes on Pro; up to 10 nodes on Enterprise (requires additional licensing).
- Job timeout: 30 seconds per job; longer tasks are split automatically, but split overhead can add ~5 seconds per sub‑job.
“We hit the API rate limit on a busy Monday morning and saw a 30 % drop in throughput. The throttling was smooth, but it forced us to rethink batch scheduling.” — Sam, DevOps Lead
Licensing, Pricing, and Support Restrictions
Beyond the feature caps, licensing and support terms can be a deal‑breaker for some teams:
- Free tier: Limited to personal/non‑commercial use; no SLA, only community forum support.
- Pro plan: Commercial use allowed; email support with 48‑hour response time; no phone or chat.
- Enterprise plan: Includes 24/7 chat, dedicated account manager, and 99.9 % uptime SLA (excluding scheduled maintenance).
- Data egress fees: First 10 GB/month free; thereafter $0.05 per GB.
- License portability: Licenses are tied to a single domain; moving to a new domain requires a new purchase.
Data Security & Compliance Considerations
LexyFill adheres to a basic security baseline, but you should verify whether it meets your industry‑specific requirements:
- Encryption: At‑rest AES‑256; in‑transit TLS 1.2+. No end‑to‑end encryption for user‑generated keys.
- Data residency: Default US‑East; EU region available on Enterprise for an extra $200/month.
- Compliance: SOC 2 Type II, GDPR. HIPAA not supported on any tier.
- Retention: Free: 30 days; Pro: 90 days; Enterprise: configurable up to 2 years.
- Audit logs: 90‑day rolling log on Pro; 12‑month log on Enterprise.
Practical Tips to Mitigate These Limits
Even with the constraints listed above, you can design your workflow to stay within LexyFill’s comfort zone:
- Batch processing: Keep each job under 500 records; this stays well below the processing‑queue depth limit.
- Schedule heavy uploads: Avoid peak hours (9 AM‑12 PM EST) to reduce the chance of hitting throttling.
- Use API token pooling: Rotate tokens across sub‑teams to stay under the 100 req/min cap on Pro.
- Offload large files to S3: Store raw assets in S3, then feed LexyFill with metadata references to stay within the 2 GB upload limit.
- Monitor usage dashboards: LexyFill provides a real‑time usage widget; set alerts at 80 % capacity for both storage and API calls.
Understanding these boundaries up front helps you plan capacity, budget for upgrades, and avoid surprise bottlenecks once you’re deep into a project.