Profile what you are about to train
Inspect full-dataset quality, preserve immutable versions, and keep content hashes attached.
Profile the full dataset, compare candidates, validate and explain the decision, then deploy on Kubernetes you control.
Sceptre turns a promising score into a reviewable operating decision.
Why evidence mattersKeep the data, experiment, model, and deployment record connected from the first profile to the final endpoint.
Inspect full-dataset quality, preserve immutable versions, and keep content hashes attached.
Compare task-specific metrics, diagnostics, parameters, and experiment history in one reviewable record.
Validate on external data, inspect leakage controls, explain feature contributions, and retain audit evidence.
Register, promote, deploy, monitor, stop, and fall back from the same project workspace.
One project record for data versions, experiments, models, deployments, and evidence
Evaluate candidates, control resource use, prove the decision, and deploy without changing tools or losing context.
Read the quick startCreate a project, upload an immutable dataset version, and uncover quality risks before training.
Confirm the task and target, choose up to 20 candidates, and review the resource estimate.
Compare task metrics, validate on external data, and explain the strongest candidates.
Register, promote, deploy, monitor, stop, and keep a fallback ready from the same workspace.
Evidence follows the model
Monitoring reconnects outcomes to the original dataset.
Help technical reviewers, risk teams, and decision makers assess the same model from one traceable source of truth.
Give a small ML or data team a repeatable operating process without assigning engineers to assemble every MLOps component.
Keep profiling, training, review, and deployment connected.
Put diagnostics, validation, explanations, and lineage beside the model choice.
Estimate demand before launch and cap every compute Job.
Retain data versions, parameters, results, artifacts, and model status inside the project.
Answers for teams evaluating a governed, self-hosted workflow.
Sceptre is a self-hosted, Kubernetes-native tabular AutoML and MLOps platform. It connects dataset profiling, model training, comparison, validation, explainability, promotion, deployment, and monitoring evidence in one project-isolated workspace.
Yes. You install Sceptre on a Kubernetes cluster using its public Helm OCI chart. The bundled PostgreSQL, SeaweedFS, and MLflow services run inside your environment; cluster operators can also configure approved external services and exposure.
Sceptre is designed for the work around and after model comparison. It keeps external validation, leakage controls, SHAP explainability, staged promotion, authenticated deployment, drift analysis, and downloadable audit evidence connected to the project.
Yes. Sceptre provides on-demand and cached SHAP explanations, historical model reconstruction, and support for non-predictive clustering estimators.
Sceptre supports CSV, Parquet, Excel, JSON, and JSONL.
Sceptre handles classification, regression, clustering, and time-series problems with task-specific ranking metrics.
Sceptre is built for small ML and data teams that already run Kubernetes, work primarily with tabular data, and need self-hosted model evidence and operations without assembling a general-purpose MLOps platform.
Not in the current release. Sceptre focuses on in-memory tabular estimators. Multi-node or distributed training requires additional infrastructure and a backend such as Dask or Ray.
The current release is documented for local development, evaluation, and compatibility testing. Production and shared-cluster environments require the controls in Sceptre's production-readiness guide.
Install the workspace, bring a tabular dataset, and follow one governed path from evidence to endpoint.