3 Downloads Updated 21 hours ago
ollama run deployxa/deployxa-lm
Updated 21 hours ago
21 hours ago
72d3437445a2 · 986MB
Build. Deploy. Scale. • Push code. Get a live URL.
Deployxa LM 1.0 is an edge-optimized, 1.5B-parameter diagnostic intelligence model trained specifically for the cloud deployment lifecycle (Docker BuildKit, Kubernetes readiness probes, dynamic port allocations, OOM limits, database migrations, and modern framework runtimes).
Running entirely within 860 MB RAM, Deployxa LM delivers performance in the same diagnostic tier as commercial frontier APIs—while operating 100% inside your private network with zero per-token fees and zero data egress.
ollama run deployxa/deployxa-lm
ollama run deployxa/deployxa-lm "Error: listen EADDRINUSE: address already in use :::3000"
docker build . 2>&1 | ollama run deployxa/deployxa-lm
Across double-blind evaluations on 384 real deployment failures across 9 polyglot ecosystems:
| Metric | Traditional Regex | Frontier Cloud API (GPT-4o) | Deployxa LM 1.0 (Ollama) |
|---|---|---|---|
| Model Footprint | Static Heuristics | ~200B+ Parameters | 1.54B Parameters (860 MB RAM) |
| Root-Cause Isolation | 40.9% | 71.4% (Recency bias) | 76.4% (Causal Multi-Hop) |
| Verified Container Recovery | N/A | 37.3% (Code refactor drift) | 48.2% (Passes HTTP readiness probes) |
| False-Alarm Rate on Warnings | 93.6% | < 3.0% | 5.8% (Filters non-fatal warnings) |
| Adversarial Injection Security | N/A | 4.0% leak rate (2⁄50) | 0 leaks / 50 test cases |
| Data Privacy | In-Cluster | Telemetry leaves VPC | 100% Local / Zero Egress |
Deployxa LM 1.0 deterministically categorizes anomalies into 15 validated failure classes:
PORT_BINDING_CONFLICT — Loopback binds (127.0.0.1) and port collisions.DATABASE_CONNECTION_UNREACHABLE — Prisma P1001, ECONNREFUSED, network partitions.DATABASE_AUTH_FAILED — Password or credential authentication rejections.DATABASE_MIGRATION_FAILED — Schema drift, pending migrations, lock contention.RUNTIME_CRASH — Unhandled TypeError, uncaught startup exceptions.DEPLOYMENT_TIMEOUT — Function 504 gateway timeouts, startup deadlines exceeded.MISSING_BUILD_OUTPUT — Missing dist/ or build/ artifact directories.AI_HALLUCINATED_IMPORT — Broken import paths (e.g. @/lib/... non-existent files).INVALID_APPLICATION_CONFIG — Missing environment variables (process.env.FOO).TYPESCRIPT_COMPILATION_ERROR — Strict compiler failures (tsc exit 1).DEPENDENCY_RESOLUTION_FAILED — npm peer conflicts (ERESOLVE), pip wheels.CONTAINER_OOM_KILLED — Out of memory / Linux OOM Killer (Exit code 137).HEALTHCHECK_PROBE_FAILED — HTTP 404⁄500 on readiness endpoints.DNS_RESOLUTION_FAILURE — Missing internal DNS service resolution.TLS_CERTIFICATE_ERROR — Expired, self-signed, or invalid SSL certificates.Deployxa LM 1.0 outputs strict, production-ready 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
}
Deployxa LM 1.0 is released under the Apache 2.0 License.
Developed by Deployxa Cloud Inc. (deployxa.com).