- If you need a full end-to-end ML platform
- If core requirements include a feature store, pipeline orchestration, model registry, monitoring, governance, and large-scale training, a platform such as Databricks, SageMaker, or Vertex AI may be more appropriate as the primary system.
- If compliance evidence is a procurement gate
- If your procurement process requires public SOC 2 Type II or ISO 27001 documentation and Prior Labs cannot provide it quickly, this can stall deals.
- If cost predictability is paramount and workloads are spiky
- Usage-based APIs can create budgeting uncertainty; self-hosted or classic model training approaches may be more controllable for some organizations.
- If your use case requires highly specialized modeling beyond tabular prediction
- Complex multimodal modeling, heavy custom architectures, or strict interpretability requirements may be better served by tailored modeling approaches.
- Model limits are explicit and versioned
- The REST API quickstart advises calling an endpoint to retrieve per-version constraints (max rows/features/classes/dataset size), indicating hard operational limits exist and may change by version.
- Scale constraints (examples from docs)
- Public model comparison documentation shows version-specific constraints such as:
- TabPFN-3 / TabPFN-3-Plus: up to 1M rows × 200 features with trade-offs, and up to 160 classes.
- TabPFN-2.6: 100K rows × 2K features, up to 10 classes.
- TabPFNv2: 10K rows × 500 features, up to 10 classes.
- These constraints can be limiting for very high-dimensional or extreme multi-class tasks.
- Roadmap / model churn risk
- The company actively releases new versions (e.g., TabPFN-3, TabPFN-2.6). This can introduce operational questions for buyers regarding:
- Backward compatibility
- Regression risk
- Model governance and reproducibility requirements