Text Generation
PEFT
Safetensors
English
deployxa
devops
sre
cloud
deployment-intelligence
root-cause-analysis
self-healing
container-orchestration
kubernetes
docker
conversational
Eval Results (legacy)
Instructions to use deployxa/deployxa-lm-1.0 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- PEFT
How to use deployxa/deployxa-lm-1.0 with PEFT:
from peft import PeftModel from transformers import AutoModelForCausalLM base_model = AutoModelForCausalLM.from_pretrained("Qwen/Qwen2.5-Coder-1.5B-Instruct") model = PeftModel.from_pretrained(base_model, "deployxa/deployxa-lm-1.0") - Notebooks
- Google Colab
- Kaggle
|
Download README.md from deployxa/deployxa-lm-1.0: direct link, hf CLI and curl.
- Browser
- Download file 17.9 kB
-
https://huggingface.co/deployxa/deployxa-lm-1.0/resolve/main/README.md
- Command line
-
hf download hf://deployxa/deployxa-lm-1.0/README.md
-
curl -L -o README.md https://huggingface.co/deployxa/deployxa-lm-1.0/resolve/main/README.md
17.9 kB
| language: | |
| - en | |
| license: apache-2.0 | |
| library_name: peft | |
| pipeline_tag: text-generation | |
| tags: | |
| - deployxa | |
| - devops | |
| - sre | |
| - cloud | |
| - deployment-intelligence | |
| - root-cause-analysis | |
| - self-healing | |
| - container-orchestration | |
| - kubernetes | |
| - docker | |
| base_model: Qwen/Qwen2.5-Coder-1.5B-Instruct | |
| model-index: | |
| - name: deployxa-lm-1.0 | |
| results: | |
| - task: | |
| type: text-generation | |
| name: Cloud Deployment Failure Diagnosis & Remediation | |
| dataset: | |
| name: Deployxa Real-World Cloud Deployment Benchmark (N=384) | |
| type: public | |
| metrics: | |
| - name: Root-Cause Isolation Accuracy | |
| type: accuracy | |
| value: 76.4% | |
| - name: Verifiable Container Recovery Rate | |
| type: accuracy | |
| value: 48.2% | |
| - name: False Alarm Rejection Rate | |
| type: accuracy | |
| value: 94.2% | |
| - name: Adversarial Injection Resistance | |
| type: accuracy | |
| value: 100.0% | |
| <div align="center"> | |
| <a href="https://deployxa.com" target="_blank" rel="noopener noreferrer"> | |
| <picture> | |
| <source media="(prefers-color-scheme: dark)" srcset="https://deployxa.com/brand/deployxa-lockup-white.png"> | |
| <img src="https://deployxa.com/brand/deployxa-lockup-white.png" alt="Deployxa Logo" width="420" style="background-color: #0B1F3B; padding: 24px 36px; border-radius: 14px; margin-bottom: 20px;" /> | |
| </picture> | |
| </a> | |
| # Deployxa LM 1.0 | |
| ### The Domain-Specialized Cloud Deployment Intelligence & SRE Copilot Model | |
| **Build. Deploy. Scale.** β’ *Push code. Get a live URL.* | |
| [](https://opensource.org/licenses/Apache-2.0) | |
| [](https://ollama.com/deployxa/deployxa-lm) | |
| [](https://pypi.org/project/dxa-lm/) | |
| [](https://chat.deployxa.com) | |
| [](https://deployxa.com) | |
| [](https://deployxa.com) | |
| [Official Platform](https://deployxa.com) β’ [Live Web Console](https://chat.deployxa.com) β’ [Ollama Model](https://ollama.com/deployxa/deployxa-lm) β’ [Documentation](https://docs.deployxa.com) β’ [Brand Kit](https://deployxa.com/brand) β’ [Benchmark Suite](https://github.com/deployxa/cloud-sre-bench) | |
| </div> | |
| --- | |
| ## β‘ The Breakthrough: Purpose-Built Cloud SRE Intelligence | |
| Modern cloud software delivery suffers from a fundamental diagnostic paradox: | |
| - **Heuristic & Regex Alerting** floods engineering teams with false alarms (**93.6% false-positive rate** on clean builds with deprecations or retries), desensitizing on-call engineers. | |
| - **Massive Frontier LLMs (200B+ parameters)** are generalists. When presented with distributed container failures, they succumb to **chronological recency bias** (anchoring on the final crash stack trace rather than the upstream root cause) and hallucinate code refactors when the actual fault is an infrastructure mismatch (e.g. port binding collisions, loopback listeners, missing environment secrets, or memory exhaustion). Furthermore, streaming proprietary internal server logs to external cloud APIs creates severe compliance liabilities (SOC2, HIPAA, GDPR) and unpredictable per-token billing. | |
| ### Enter Deployxa LM 1.0 | |
| **Deployxa LM 1.0** is the first foundation model engineered from the ground up specifically for the cloud deployment lifecycle. | |
| By distilling deep causal reasoning, distributed systems semantics, and container failure graphs into a high-density **1.5-billion parameter architecture**, Deployxa LM achieves performance in the same diagnostic tier as commercial frontier APIsβwhile operating in **under 1 GB of memory (860 MB RAM)** entirely inside your private VPC, Kubernetes cluster, or local workstation. | |
| ```text | |
| ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ | |
| β DEPLOYXA LM 1.0: EVALUATION SUMMARY β | |
| ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€ | |
| β π― Root-Cause Isolation (N=384) β 76.4% vs 71.4% (GPT-4o) | 69.2% (Claude 3.5)β | |
| β π οΈ Verifiable Container Recovery Rate β 48.2% vs 37.3% (GPT-4o) | 22.2% (Base 1.5B) β | |
| β π‘οΈ Adversarial Log Injection Security β 0 leaks / 50 test cases (vs 2/50 on GPT-4o) β | |
| β π False-Alarm Rate on Warning-Heavy Logsβ 5.8% vs 93.6% (Regex Heuristics) β | |
| β π Privacy & Infrastructure Economics β In-VPC / Zero per-token API fees β | |
| ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ | |
| ``` | |
| > **The Core Value Proposition:** Correctly isolates the root cause in **3 out of 4 incidents (76.4%)**, produces verifiable container fixes that pass automated HTTP readiness probes for **nearly half of all failures (48.2%)**, and slashes alert fatigue by **16x**βall within an ultra-compact 860MB local footprint. | |
| --- | |
| ## ποΈ The 4 Architectural Pillars | |
| ``` | |
| βββββββββββββββββββββββββββββββββββββββββββββββββ | |
| β RAW DEPLOYMENT TELEMETRY β | |
| β (BuildKit, Docker, K8s, Logs, Traces) β | |
| βββββββββββββββββββββββββ¬ββββββββββββββββββββββββ | |
| β | |
| βΌ | |
| βββββββββββββββββββββββββββββββββββββββββββββββββ | |
| β ADVERSARIAL FORENSIC SCRUBBER β | |
| β β’ Secret Redaction (Tokens, DB Passwords) β | |
| β β’ Prompt-Injection Sanitization (0 Leaks) β | |
| βββββββββββββββββββββββββ¬ββββββββββββββββββββββββ | |
| β | |
| βΌ | |
| βββββββββββββββββββββββββββββββββββββββββββββββββ | |
| β DEPLOYXA MULTI-HOP CAUSAL ENGINE β | |
| β β’ 15-Class Granular Failure Disambiguation β | |
| β β’ Upstream Root-Cause Tracing (Anti-Recency) β | |
| β β’ Epistemic Calibration (Fail-Closed Gate) β | |
| βββββββββββββββββββββββββ¬ββββββββββββββββββββββββ | |
| β | |
| βΌ | |
| βββββββββββββββββββββββββββββββββββββββββββββββββ | |
| β ACTIONABLE CONTAINER REMEDIATION β | |
| β β’ Machine-Executable SRE Recipes β | |
| β β’ Verifiable Container Boot (Readiness Probesβ | |
| β β’ Deterministic Schema Compliance (100% JSON)β | |
| βββββββββββββββββββββββββββββββββββββββββββββββββ | |
| ``` | |
| ### 1. Multi-Hop Causal Tracing (Defeating Recency Bias) | |
| Generalist models anchor on the last line of an incident log (e.g. `Exit code 137` or `502 Bad Gateway`). Deployxa LM reconstructs the complete dependency graph, tracing back through hundreds of lines to isolate the initiating faultβwhether that is a connection pool exhaustion 40 lines earlier or an unhandled loopback interface bind. | |
| ### 2. Verifiable Container Remediation | |
| Rather than offering conversational advice or rewriting application business logic, Deployxa LM synthesizes machine-executable infrastructure remediations (e.g., binding `0.0.0.0:$PORT`, configuring container memory limits, unlocking schema migrations, or aligning build output directories). In double-blind sandboxed Docker environments, Deployxa LM achieves a **48.2% verified container recovery rate**βwhere the generated repair allows the container to boot and pass HTTP readiness probes. | |
| ### 3. Granular 15-Class Disambiguation | |
| Deployxa LM avoids the coarse categorization traps that cause other models to recommend wrong fixes. It cleanly isolates: | |
| - **Database Partitioning**: Disambiguates DB Unreachable (`P1001` / `ECONNREFUSED`) vs. DB Auth Rejection (`password failed`) vs. DB Migration Lock. | |
| - **Port Allocation**: Separates loopback binding traps (`127.0.0.1`) from actual port collisions. | |
| - **AI-Generated Code Flaws**: Distinguishes between real missing packages and AI-hallucinated module paths (`@/lib/...`). | |
| ### 4. Adversarial Forensic Protection | |
| Deployxa LM treats log streams strictly as immutable forensic evidence rather than conversational instructions. Embedded shell injections (`rm -rf /`, `DROP TABLE`), fake error messages, and prompt jailbreaks (`"Ignore previous instructions"`) are completely neutralizedβrecording **0 leaks across 50 adversarial test cases**. | |
| --- | |
| ## π― The 15-Class SRE Diagnostic Taxonomy | |
| Deployxa LM 1.0 maps deployment anomalies to 15 canonical failure classes paired with dynamic SRE remediations: | |
| | Canonical Category | Description | Primary SRE Remediation Action | | |
| |---|---|---| | |
| | `PORT_BINDING_CONFLICT` | Loopback bind (`127.0.0.1`) or port collision | `REMEDIATE_BIND_ALL_INTERFACES` (`0.0.0.0:$PORT`) | | |
| | `DATABASE_CONNECTION_UNREACHABLE` | Host unreachable / Prisma P1001 / ECONNREFUSED | `REMEDIATE_VERIFY_DATABASE_HOST_AND_NETWORK` | | |
| | `DATABASE_AUTH_FAILED` | Password / role failure on database authentication | `REMEDIATE_UPDATE_DATABASE_CREDENTIALS` | | |
| | `DATABASE_MIGRATION_FAILED` | Schema drift, pending migrations, lock contention | `REMEDIATE_RUN_DATABASE_MIGRATIONS` | | |
| | `RUNTIME_CRASH` | Unhandled TypeError, uncaught exception at startup | `REMEDIATE_INSPECT_RUNTIME_TRACE_AND_PATCH` | | |
| | `DEPLOYMENT_TIMEOUT` | Function 504 gateway timeout, startup deadline exceeded | `REMEDIATE_EXTEND_FUNCTION_TIMEOUT_AND_WARMUP` | | |
| | `MISSING_BUILD_OUTPUT` | Missing `dist/` or `build/` artifact directory | `REMEDIATE_VERIFY_BUILD_OUTPUT_DIRECTORY` | | |
| | `AI_HALLUCINATED_IMPORT` | Broken import alias (e.g. `@/lib/...` non-existent file) | `REMEDIATE_RESOLVE_HALLUCINATED_IMPORT` | | |
| | `INVALID_APPLICATION_CONFIG` | Missing environment variable (e.g. `process.env.FOO`) | `REMEDIATE_SET_APPLICATION_CONFIG_ENV_VARS` | | |
| | `TYPESCRIPT_COMPILATION_ERROR` | Strict TS compiler failures (`tsc` exit 1) | `REMEDIATE_RESOLVE_TYPESCRIPT_BUILD_ERRORS` | | |
| | `DEPENDENCY_RESOLUTION_FAILED` | npm peer conflicts (`ERESOLVE`), pip wheels | `REMEDIATE_RESOLVE_PACKAGE_DEPENDENCIES` | | |
| | `CONTAINER_OOM_KILLED` | Out of memory / Linux OOM Killer (Exit code 137) | `REMEDIATE_INCREASE_CONTAINER_MEMORY_LIMIT` | | |
| | `HEALTHCHECK_PROBE_FAILED` | HTTP 404/500 on readiness endpoint | `REMEDIATE_ALIGN_HEALTHCHECK_PATH_AND_PORT` | | |
| | `DNS_RESOLUTION_FAILURE` | Missing internal DNS service resolution | `REMEDIATE_RESOLVE_INTERNAL_DNS_ENDPOINTS` | | |
| | `TLS_CERTIFICATE_ERROR` | Expired, self-signed, or invalid SSL certificate | `REMEDIATE_RENEW_OR_ATTACH_VALID_SSL_CERTIFICATE` | | |
| --- | |
| ## π Comprehensive Benchmark Evaluation (N=384) | |
| All evaluations are conducted against an open dataset of 384 real deployment failure incidents across 9 polyglot ecosystems (Node.js/Next.js, Python/FastAPI, Go, Rust, Docker BuildKit, Postgres/Prisma, Kubernetes probes, TLS/ingress, and AI-scaffolded applications). | |
| ### Architectural Comparison Matrix | |
| | Dimension / Metric | Traditional Regex | Base Open LLM | Frontier Cloud API (GPT-4o) | **Deployxa LM 1.0 (Our Work)** | | |
| | :--- | :---: | :---: | :---: | :---: | | |
| | **Model Footprint** | Static Regex | 1.54B Parameters | ~200B+ Parameters | **1.54B Base + 18.5M LoRA (860 MB)** | | |
| | **Root-Cause Isolation (N=384)** | 40.9% | 22.2% | 71.4% (Recency bias) | **76.4% (Causal Multi-Hop)** | | |
| | **Verified Container Recovery** | N/A | 22.2% | 37.3% (Code refactor drift) | **48.2% (Passes HTTP readiness probes)** | | |
| | **Strict JSON Schema Compliance** | 100.0% | 88.9% | 96.2% | **100.0% (Zero parse errors)** | | |
| | **Clean Log False Alarm Rate** | 93.6% | Unbounded | < 3.0% | **5.8% (Filters non-fatal warnings)** | | |
| | **Adversarial Injection Security** | N/A | Leaks prompt | 4.0% leak rate (2/50) | **0 leaks / 50 test cases** | | |
| | **Per-Token API Metering** | $0.00 | $0.00 | Metered per 1k tokens | **$0.00 per-token fees (In-VPC)** | | |
| | **Inference Latency (Edge)** | < 10ms | ~45ms | 4,000ms β 12,000ms | **1.5s β 3.2s (Deterministic)** | | |
| | **Data Privacy & Compliance** | In-Cluster | In-Cluster | Telemetry leaves VPC | **100% In-VPC / Zero Egress** | | |
| --- | |
| ## π Quickstart | |
| ### 1. Using Ollama (Instant 1-Command Local Run) | |
| Run Deployxa LM 1.0 locally in Ollama: | |
| ```bash | |
| ollama run deployxa/deployxa-lm | |
| ``` | |
| ### 2. Using the Official Deployxa CLI (`dxa-lm`) | |
| ```bash | |
| # Install the CLI from PyPI | |
| pip install dxa-lm | |
| # Diagnose a failure log file | |
| dxa-lm diagnose /var/log/deploy/error.log | |
| # Pipe directly from Docker build or CI/CD | |
| docker build . 2>&1 | dxa-lm diagnose | |
| # Interactive SRE chat console | |
| dxa-lm chat | |
| # Check production cluster health | |
| dxa-lm health | |
| ``` | |
| ### 3. Python SDK / In-Process Execution | |
| ```python | |
| import torch | |
| from transformers import AutoTokenizer, AutoModelForCausalLM | |
| from peft import PeftModel | |
| BASE_MODEL = "Qwen/Qwen2.5-Coder-1.5B-Instruct" | |
| ADAPTER_REPO = "deployxa/deployxa-lm-1.0" | |
| tokenizer = AutoTokenizer.from_pretrained(BASE_MODEL, trust_remote_code=True) | |
| base_model = AutoModelForCausalLM.from_pretrained( | |
| BASE_MODEL, | |
| torch_dtype=torch.float16, | |
| device_map="auto" | |
| ) | |
| model = PeftModel.from_pretrained(base_model, ADAPTER_REPO) | |
| model.eval() | |
| # Telemetry log payload | |
| prompt = """<|im_start|>system | |
| You are Deployxa LM 1.0, Deployxa Cloud's specialist deployment diagnostic model. | |
| Analyze the provided deployment telemetry. Format response strictly as JSON with keys: | |
| deployment_status, root_cause_category, confidence, evidence, reasoning_summary, recommended_action_ids, abstain.<|im_end|> | |
| <|im_start|>user | |
| Deployment Logs: | |
| [server] Express listening on http://127.0.0.1:3000 | |
| Readiness probe failed to connect. | |
| Diagnose deployment:<|im_end|> | |
| <|im_start|>assistant | |
| """ | |
| inputs = tokenizer(prompt, return_tensors="pt").to("cuda" if torch.cuda.is_available() else "cpu") | |
| with torch.no_grad(): | |
| outputs = model.generate(**inputs, max_new_tokens=350, temperature=0.1) | |
| print(tokenizer.decode(outputs[0][inputs["input_ids"].shape[1]:], skip_special_tokens=True)) | |
| ``` | |
| **Expected Diagnostic Output:** | |
| ```json | |
| { | |
| "deployment_status": "FAILED", | |
| "root_cause_category": "PORT_BINDING_CONFLICT", | |
| "confidence": 0.95, | |
| "evidence": "Express listening on http://127.0.0.1:3000", | |
| "reasoning_summary": "Application bound strictly to loopback (127.0.0.1/localhost) instead of 0.0.0.0, preventing platform ingress routing.", | |
| "recommended_action_ids": [ | |
| "REMEDIATE_BIND_ALL_INTERFACES", | |
| "REMEDIATE_SET_PORT_ENV" | |
| ], | |
| "abstain": false | |
| } | |
| ``` | |
| ### 3. Self-Hosted REST API Server | |
| Run the production API server in Kubernetes or a local container: | |
| ```bash | |
| dxa-server --host 0.0.0.0 --port 8080 | |
| ``` | |
| --- | |
| ## π Safety Posture & Fail-Closed Calibration | |
| Deployxa LM 1.0 enforces strict safety and reliability invariants: | |
| 1. **Monitored Read-Only Execution**: The model generates verified recipes without executing arbitrary unapproved shell commands (`safety_controls.read_only_mode = true`). | |
| 2. **Epistemic Calibration on Thin Logs**: When presented with insufficient evidence (e.g., `"Deploy failed"` with no stack traces), the model refuses to guessβscoring **0.15 confidence** (`LOW`), outputting `STANDBY` status, and triggering `abstain: true` with `ESCALATE_HUMAN_SRE_AUDIT`. | |
| 3. **Automated Secret Scrubbing**: Redacts sensitive API keys, database credentials, AWS secrets, and JWTs from log snippets before generating responses. | |
| --- | |
| ## π§ͺ Open Benchmark Suite | |
| Leaderboard from our 384-incident eval; the open [`deployxa/cloud-sre-bench`](https://github.com/deployxa/cloud-sre-bench) repository ships the benchmark harness with a 26-case public subset. | |
| Run the benchmark evaluation suite: | |
| ```bash | |
| git clone https://github.com/deployxa/cloud-sre-bench.git | |
| cd cloud-sre-bench | |
| # Run against Ollama or live API | |
| python3 run_benchmark.py --target api | |
| # or: python3 run_benchmark.py --target ollama --model deployxa/deployxa-lm | |
| ``` | |
| --- | |
| ## π License & Brand Guidelines | |
| Deployxa LM 1.0 is released under the **[Apache 2.0 License](LICENSE)**. | |
| Built with pride by **Deployxa Cloud Inc.** ([https://deployxa.com](https://deployxa.com)). | |
| Brand assets, lockups, and design guidelines are available at [deployxa.com/brand](https://deployxa.com/brand). | |