Xlstm is live · custom pricing · last verified 4 Nov 2026 · viability monitor

Xlstm

Xlstm

NXAI builds xLSTM memory architectures for edge and industrial time-series work, shipping TiRex-1 and TiRex-2 models on Hugging Face and GitHub.

61/100MonitorCustom pricingContact Sales

Choose NXAI and xLSTM when your constraint is state-tracking or edge inference on time-series data and you have in-house ML depth to run TiRex-1 or TiRex-2 from the published Hugging Face weights and GitHub code. The scope is deliberately narrow — univariate and multivariate time series — and the site frames robotics and large-scale world models as tomorrow's work, not today's. If you need a managed forecasting platform with a dashboard and onboarding, take the managed route instead. If you want a general-purpose hosted LLM, this is the wrong shelf entirely. Treat an NXAI engagement as a research partnership, and budget for owning your own integration and edge validation.

Verdict generated

Verified 9d ago · liveness 61/100 · cite: rightaichoice.com/tools/xlstm

Best for
  • Industrial time-series teams needing edge-deployable models
  • Edge AI engineers optimizing latency and compute
  • ML research groups exploring Transformer alternatives
  • Robotics researchers working on state-tracking
Not ideal for
  • Teams without in-house deep learning expertise
  • Organizations wanting a fully managed SaaS platform
  • Buyers who need a general-purpose hosted LLM
Visit Website

AdvancedFor an ML engineer comfortable with Hugging Face and PyTorch-style workflows: hours to pull TiRex-1 or TiRex-2 and run a first inference. Days to a working benchmark on your own data. Weeks to production edge deployment, because hardware validation, serving, and monitoring are yours to build. Teams without in-house deep learning staff should expect substantially longer.Web · API · CLIAPI availableVerified 9d ago
Pricing
Custom pricing
Contact Sales3 hidden costs
Learning curve
Advanced
For an ML engineer comfortable with Hugging Face and PyTorch-style workflows: hours to pull TiRex-1 or TiRex-2 and run a first inference. Days to a working benchmark on your own data. Weeks to production edge deployment, because hardware validation, serving, and monitoring are yours to build. Teams without in-house deep learning staff should expect substantially longer.
Runs on
WebAPICLI
API available
Who it's for
Edge AI engineer at an industrial manufacturerML research lead exploring non-Transformer sequence modelsData science team lead at an energy or utilities operator
Live sentiment
Is Xlstm actually worth it?

We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.

  • Honest verdict, not marketing
  • Real pros & cons from real users
  • Attributed quotes with receipts
Run a free scan

3 free scans · no card needed

Skip it if

Skip NXAI if you need a ready-to-run forecasting API or a managed platform with a dashboard, rather than open model weights you integrate and deploy yourself.

Skip-it-if note generated
The 30-second take
Biggest gripe

The weights are free but the integration isn't — you fund the engineering time to serve, monitor, and update TiRex-1 or TiRex-2 yourself.

Price reality

Xlstm's pricing fits teams whose volume aligns with the published tiers. Compare against the alternatives listed below for stage-specific value.

Generated

In short

Xlstm — NXAI builds xLSTM memory architectures for edge and industrial time-series work, shipping TiRex-1 and TiRex-2 models on Hugging Face and GitHub. Best for Industrial time-series teams needing edge-deployable models, Edge AI engineers optimizing latency and compute, ML research groups exploring Transformer alternatives. Pricing is on request (custom quotes).

Claim this listing

What is Xlstm?

Xlstm — NXAI builds xLSTM memory architectures for edge and industrial time-series work, shipping TiRex-1 and TiRex-2 models on Hugging Face and GitHub. Best for Industrial time-series teams needing edge-deployable models, Edge AI engineers optimizing latency and compute, ML research groups exploring Transformer alternatives. Pricing is on request (custom quotes).

Contact SalesAdvancedAPI availableWeb · API · CLI

NXAI is a frontier AI lab based in Linz, Austria, building AI on its proprietary xLSTM (Extended Long Short-Term Memory) architecture — a modernization of the classic LSTM with sophisticated memory hierarchies, designed for long-range state-tracking. The company's Chief Scientist and co-founder is Prof. Dr. Sepp Hochreiter, one of the fathers of modern deep learning, and it works closely with JKU Linz and other research institutions. The shipped products are narrow and specific: TiRex-1 handles univariate time-series analysis and TiRex-2 handles multivariate time-series analysis, aimed at industrial edge, embedded, and forecasting deployments where the company states its models deliver 50× impact. NXAI runs its xLSTM models in a cloud environment but focuses on edge applications, using an in-house edge lab to validate real-world deployment. Model weights are published on Hugging Face and source code on GitHub, so teams work directly from the models rather than through a packaged product. The stated roadmap points to large-scale world models built on neural memory hierarchies and memory routing, with robotics as the primary application — described on the site as future work, not shipped product. This is a research-lab relationship model: you bring ML engineering depth, and NXAI brings the architecture. It suits engineering and research groups optimizing for state-tracking efficiency and edge inference; it is a poor fit if you want a hosted, plug-and-play forecasting API.

Key features

  • Proprietary xLSTM (Extended Long Short-Term Memory) architecture
  • Sophisticated memory hierarchies for long-range state-tracking
  • TiRex-1 for univariate time-series analysis
  • TiRex-2 for multivariate time-series analysis
  • Cloud deployment of xLSTM models
  • Edge and embedded deployment focus
  • In-house edge lab for real-world deployment validation
  • Neural memory hierarchies and memory routing (stated future direction)
  • Open model weights published on Hugging Face
  • Source code published on GitHub
  • Optimized for faster inference than Transformer baselines
  • Targets lower operational costs on industrial workloads
  • Models developed in Linz, Austria
  • Claimed top positions on globally recognized leaderboards

Behind the verdict

NXAI is unusual in the 2026 AI vendor landscape because it is selling an architecture rather than a subscription. The core claim — that xLSTM's memory hierarchies outperform Transformer baselines on state-tracking — is the whole product thesis, and everything shipped follows from it. What you actually get today is two time-series models. TiRex-1 covers univariate series; TiRex-2 covers multivariate series. Both are published as open weights on Hugging Face with code on GitHub, which means the integration, serving layer, monitoring, and edge packaging are yours to build. That is a real strength for teams who want to inspect and modify the model, and a real cost for teams who don't. The deployment story is the most differentiated part. NXAI runs xLSTM in the cloud but explicitly focuses on edge and embedded applications, backed by an in-house edge lab used to validate real-world deployment. For industrial settings where a cloud round-trip is too slow or connectivity is unreliable, that focus matters more than benchmark placement. The company also cites top positions on globally recognized leaderboards, and its research lineage is legitimate: Sepp Hochreiter as Chief Scientist and co-founder, with close JKU Linz ties, is about as strong a research credential as this category offers. Where it does not fit: the delivered scope. Time series, univariate and multivariate, is what ships. Robotics state-tracking and neural-memory world models are described as the next phase. If your use case sits outside time series today, you are buying a roadmap, not a product. The published-material-only model also means no managed dashboard to evaluate, no packaged onboarding flow, and no plug-and-play API you can test this afternoon — you evaluate the models on Hugging Face or you talk to the lab. For organizations without deep learning engineers on staff, that gap is decisive. For research groups and edge AI teams who already speak the language, it removes a layer of abstraction between them and the architecture.

Models under the hood

xLSTMTiRex-1TiRex-2

as of 2026-11-03

Limitations

  • The shipped products are narrow.
  • TiRex-1 covers univariate time-series and TiRex-2 covers multivariate time-series; robotics and large-scale world models are described on the site as future work.
  • Model weights come from Hugging Face and code from GitHub, so you own the integration, serving, and edge packaging work.
  • Deployment spans cloud and — with the stated edge and embedded focus — requires edge-lab-validated integration effort.
  • The company's own material does not detail a managed dashboard or packaged onboarding flow.
  • If your problem is outside time-series state-tracking, the delivered product likely does not cover it yet.

as of 2026-10-10

Researching Xlstm? Get your full AI stack in 60 seconds.

Free, no signup — tell us your goal and get tools matched to your budget & existing stack.

Is Xlstm still active?

Xlstm is live · custom pricing · last verified 4 Nov 2026 · viability monitor.

Viability score

61/100
Monitor

How well maintained and how widely used is Xlstm? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this

Recent activity
not measured
Traction
100
Site health
95
User sentiment
59
What the vendor publishes
0

Last calculated: November 2026

How we score →

What do users say about Xlstm?

What people actually say about Xlstm — is it worth it?

Our community sentiment research written Jul 15, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.

How we verified this

Every listed fact about Xlstm — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 4 Nov 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.

Verification history

We have re-verified Xlstm 12 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.

  1. — changed SSL certificate
  2. — changed switching out, limitations, summary, switching in, hidden costs, use cases, our verdict, description, who should skip it, setup time, features, who it suits, pricing fit
  3. — changed limitations
  4. — changed features, who it suits, description, our verdict, hidden costs, limitations, switching in, switching out, models, who should skip it, pricing fit, setup time, summary, use cases
  5. — changed SSL certificate, domain expiry
  6. — changed SSL certificate

Showing the 6 most recent of 12 verification passes.

Free to cite with attribution — this page re-verifies continuously.

Claim this listing

How much does Xlstm cost in 2026?

Xlstm: Pricing is on request (custom quotes). Pricing last verified 4 Nov 2026.

Hidden costs & gotchas

What the public pricing page doesn't put in bold. Captured from pricing-page footnotes, contract terms, and recurring complaints.

  • The weights are free but the integration isn't — you fund the engineering time to serve, monitor, and update TiRex-1 or TiRex-2 yourself.
  • Edge deployment carries its own bill: hardware selection and validation against your latency and power envelope are on you, not the vendor.
  • Working from published code means you also own versioning and re-validation whenever the models are updated.

Where the pricing makes sense

The company stage and team size where Xlstm's pricing actually pencils out — and where peers do it cheaper.

Xlstm's pricing fits teams whose volume aligns with the published tiers. Compare against the alternatives listed below for stage-specific value.

Hidden-cost and price-fit notes generated

Has Xlstm's pricing changed?

No plan price for Xlstm has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.

Who should pick Xlstm?

Pick Xlstm if you are Industrial time-series teams needing edge-deployable models, Edge AI engineers optimizing latency and compute, ML research groups exploring Transformer alternatives, Robotics researchers working on state-tracking.

Look elsewhere if you are Teams without in-house deep learning expertise, Organizations wanting a fully managed SaaS platform, Buyers who need a general-purpose hosted LLM.

Skip it if Skip NXAI if you need a ready-to-run forecasting API or a managed platform with a dashboard, rather than open model weights you integrate and deploy yourself.

Generated

Real-world workflow fit

Concrete scenarios for the personas Xlstm actually fits — and what changes day-one when you adopt it.

Edge AI engineer at an industrial manufacturer

Pull TiRex-1 weights from Hugging Face, benchmark them against the existing Transformer forecasting model on a month of plant sensor data, then containerize the winner for a gateway device.

Outcome: A concrete latency-and-accuracy comparison on your own data before any commercial conversation with NXAI.

ML research lead exploring non-Transformer sequence models

Clone the GitHub code for xLSTM and run an ablation on long-range state-tracking against a Transformer baseline, using TiRex-2 for a multivariate sensor dataset.

Outcome: A reproducible internal benchmark, plus a documented basis for deciding whether to contact the lab about a deeper collaboration.

Data science team lead at an energy or utilities operator

Stand up a TiRex-1 forecast for load or demand series in a staging environment, compare inference cost per prediction against the current cloud model, and assess whether edge placement is feasible.

Outcome: A cost-per-forecast number and a go/no-go on edge placement, before committing engineering headcount.

Workflow scenarios generated

Use cases

Setup time & first value

How long it actually takes to get something useful out of Xlstm — broken out by persona, not the marketing-page minute.

For an ML engineer comfortable with Hugging Face and PyTorch-style workflows: hours to pull TiRex-1 or TiRex-2 and run a first inference. Days to a working benchmark on your own data. Weeks to production edge deployment, because hardware validation, serving, and monitoring are yours to build. Teams without in-house deep learning staff should expect substantially longer.

Switching to or from Xlstm

How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.

Migrating in
  • →From a Transformer forecasting baseline: retrain or fine-tune TiRex-1 or TiRex-2 on your series and benchmark inference latency on the same hardware envelope before switching.
  • →From a managed cloud forecasting API: keep the API in place while you stand up the open-weights model locally, then shift workloads once edge latency is measured.
  • →From a classical time-series library (ARIMA, ETS): keep the statistical model as a baseline, since it costs nothing to run alongside and gives you a sanity check on xLSTM outputs.
Migrating out
  • ↗To a managed forecasting platform: export your training data and re-onboard to the platform's API, accepting less control over the model internals.
  • ↗To a Transformer-based time-series model: retrain on the same series and re-tune the serving stack, since the inference characteristics differ.

Tutorials & Learning

YouTube returned 6 videos for “Xlstm”, and we withheld 6: 6 could not be judged, because “Xlstm” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Xlstm.

Official links

What are the best Xlstm alternatives?

The closest alternatives to Xlstm we list are Hugging Face, Transformers and Small Doge. Ranked by direct product-type match, not category overlap.

Closest alternatives to Xlstm
AlternativePricingStarts atLast verified
Hugging FaceFreemiumPricing not published—
TransformersFreemiumPricing not published—
Small DogeFreeFree—

Alternatives to Xlstm

View all
Hugging Face

Hugging Face

Browse 2M+ open models, 500k+ datasets and 1M+ Spaces on the Hugging Face machine learning hub

FreemiumTry
Transformers

Transformers

Transformers is Hugging Face's open-source model-definition framework for running, fine-tuning, and serving text, vision, audio, and

FreemiumTry
Small Doge

Small Doge

SmallDoge small language models: open SLM weights, training checkpoints, and SLM datasets on Hugging Face

FreeTry

Tools that pair well with Xlstm

Common stack mates teams adopt alongside Xlstm, with the specific reason each pairing earns its keep.

Xlstm vs its closest rival

Xlstm's closest head-to-head is with Surge Ai.

Our Xlstm vs Surge Ai verdict written Jul 8, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.

Frequently asked questions

For makers of Xlstm

Used Xlstm? Help shape our editorial sentiment research.