Ember Data can be used separately from Ember itself. In fact, the official documentation treats them as if they are. It's even a separate project on GitHub:
https://github.com/emberjs/data
In Airbnb Is Moving Faster at Scale with GraphQL and Apollowarp-drive-data
warp-drive
TypeScript2012–2019
warp-drive-data / warp-drive
warp-drive
WarpDrive is the lightweight data library for ambitious web apps — universal, typed, reactive, and ready to scale.
16Distinct people
19Mentions
0Explicit recommenders
3.2KGitHub stars
What to know before exploring
What it is
WarpDrive is the lightweight data library for ambitious web apps — universal, typed, reactive, and ready to scale.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year19 dated mentions
Observed mentions: 2012-02-16 12:20:53 UTC to 2019-01-13 01:38:13 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 10 | 0 | 10 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
WarpDrive is the lightweight data library for web apps —
universal, typed, reactive, and ready to scale.
WarpDrive makes it easy to build scalable, fast, feature
rich applications — letting you ship better experiences more quickly without re-architecting your app or API. WarpDrive is:
🌌 Seamless Reactivity in any Framework
⚡️ Committed to Best-In-Class Performance
💚 Typed
⚛️ Works with any API
🌲 Focused on being as tiny as possible
🚀 SSR Ready
🐹 Built with ♥️ by Ember
Get Started → Guides
Quick Links
Installation
API Docs
Guides
Ember Compatibility
The Big List of Versions
Contributing
Community & Help
RFCs
Team
Blog
Ember Compatibility
The following table lists WarpDrive versions alongside information about
ember compatibility.
Lockstep: the latest version of ember-source at the time of release
Supported: the versions of ember-source the release officially supports
Tested: the versions of ember-source the project tested this release against
Range: the peer-dep range the release states for ember-source
The library is often compatible with a larger range than was officially supported at
the time of release, and we make an effort to test against a larger range than we officially
state is supported. In many cases it will be compatible for a larger range than is shown here.
Where possible, we try to maintain this larger window of support as long as possible, but if
it does become necessary to break compatibility with an older, unsupported release we do not
consider it a breaking change.
The table is generated from this data using the
command pnpm sync-readme-tables.
Status
WarpDrive
Lockstep
Supported
Tested
Range
✅
Canary
6.4
4.8
4.12
5.*
6.*
3.28
4.12
5.12
6.12
3.28.12
>= 4.*
>= 5.*
>= 6.*
✅
Beta
6.4
4.8
4.12
5.*
6.*
3.28
4.12
5.12
6.12
3.28.12
>= 4.*
>= 5.*
>= 6.*
✅
Latest (Stable)
>= 5.3
6.0
6.1
6.2
6.3
4.8
4.12
5.*
6.*
3.28
4.12
5.12
6.12
3.28.12
>= 4.*
>= 5.*
>= 6.*
✅
LTS
>= 5.3
6.0
6.1
6.2
6.3
4.8
4.12
5.*
6.*
3.28
4.12
5.12
6.12
3.28.12
>= 4.*
>= 5.*
>= 6.*
✅
V4 Special Release
(vite support)1
6.3
4.*
5.*
6.*
3.28
4.4
4.8
4.12
5.4
5.8
5.12
6.3
3.28.12
>= 4.*
>= 5.*
>= 6.*
❌
(unsupported)
Prior LTS
4.12.3
4.*
5.*
3.28
4.4
4.8
4.12
5.0
3.28.12
>= 4.*
>= 5.*
❌
(unsupported)
Prior LTS
4.8.6
4.*
3.28
4.4
4.8
3.28.12
>= 4.*
⚠️
(unsupported)
ModelFragments2
4.6.0
3.28
4.*
3.28
4.4
4.5
4.6
3.28.12
>= 4.*
⚠️
(unsupported)
Prior LTS2
4.4.5
3.28
4.*
3.28
4.4
3.28.12
>= 4.*
⚠️
(unsupported)
Prior LTS3
3.28.12
3.*
4.*
3.20
3.24
3.28
>= 3.*
>= 4.*
The Big List of Versions
The table below is generated using the command pnpm sync-readme-tables.
Package
Audience
Canary
Beta
Stable
LTS
V4-Canary
LTS-4-12
warp-drive
🌌
eslint-plugin-warp-drive
🌌
ember-data
🐹
@warp-drive/schema-record
🌌
@warp-drive/holodeck
🌌
@warp-drive/experiments
🌌
@warp-drive/ember
🐹
@warp-drive/diagnostic
🌌
@warp-drive/core-types
🌌
@warp-drive/build-config
🌌
@ember-data/tracking
🌌🐹
@ember-data/store
🌌
@ember-data/serializer
🐹
@ember-data/rest
🌌
@ember-data/request-utils
🌌
@ember-data/request
🌌
@ember-data/model
🐹
@ember-data/legacy-compat
🐹
@ember-data/json-api
🌌🐹
@ember-data/graph
🌌
@ember-data/debug
🐹
@ember-data/codemods
🐹
@ember-data/adapter
🐹
@ember-data/active-record
🌌
Code of Conduct
Refer to the Code of Conduct for community guidelines and inclusivity.
License
This project is licensed under the MIT License.
Footnotes
Special release to support vite builds in apps using 4.x ↩
This version may receive special long-term patches to assist model-fragments users in creating a migration path onto 5.x and off of ModelFragments ↩ ↩2
Special updates have occurred to extend support to ember-source v5 and v6 ↩
Read the full README on GitHubWhat Hacker News says
19 sourcesIs there any differentiation between the two on API stability?
I got burned last fall trying to build an app with Ember as they kept making breaking changes, even between release candidates (!). Technically Ember was stable, but Ember Data (which is separate I guess?) was doing major refactoring on their API, and it cost us quite a bit of time just trying to keep up. Even today, their GitHub has a disclaimer that it's beta quality and under active development[1]. Ember CLI also says it's very much WIP[2], even though it seems to be the officially endorsed way to build Ember apps.
Does Angular make stronger promises about their stability? Is this sort of thing just the cost of doing business with cutting-edge frameworks? Or am I missing something?
[1]: https://github.com/emberjs/data#api-stability
[2]: http://www.ember-cli.com/#community
In Rails JS frameworks: Ember.js vs. AngularJSReplying to the sibling. There was documentation of how the names changed - you just need to know where to look:
https://github.com/emberjs/data/blob/master/TRANSITION.md
In Ember TutorialI started a major rewrite for a Rails App that I'm converting to Rails API + Ember with Ember Data. Yeah, the learning curve has been huge and Ember Data pretty much didn't help things. But, I've stuck with it and everytime I struggle with something (happened first with routing nested resources - still feels a bit magic sometimes), I take a step back and look at the Ember way of doing things and I usually become enlightened with the very well thought out decisions.
For those of you struggling with Ember Data - this is your best friend - https://github.com/emberjs/data/blob/master/TRANSITION.md probably the best documentation on the matter. If you got Active Model Serializers, use the right serializer on Ember data side to get going.
IF you're using Ember Rails - be sure to check that it's pulling the latest Ember Data.
I like that there a
Read the rest
re more tutorials and demos coming out but seriously, we need some more non-trivial UI examples. Maybe after my project I'll write up a blog post if anyone here is interested.
It should work for you. I followed along with the screencast (Truly awesome stuff. Build a blog in under 30 minutes!? Amazing.) using the Starter Kit 1.0.0-RC.2 which is what you would've downloaded yesterday. Everything worked fine for me. Ah, except for the Ember Data component which initially caused me problems. Turns out you have to grab it from Git and build it yourself. I only found that out from the comments on the video where it was posted on YouTube. That said, once I followed the directions I found on YouTube and built Ember Data, everything worked great and went smoothly from there on out.
Here are the instructions for building Ember Data (from a random YouTube comment):
git clone git://github.com/emberjs/data.git
cd data
bundle install
rake
You need to have bundler installed for your version of ruby.
Then go to dist/ember-da
Read the rest
ta.js and use that where it says "ember-data-master.js" in the video. Worked for me.
Thank you for the detailed feedback. Working on Ember Data has been one of the most challenging efforts of my career, but I think that it has the opportunity to dramatically change how people write web applications. Once we've stabilized it, of course. :)
Here are the specific steps we're taking to address your concerns:
1. Thanks to a pull request from Stanley Stuart[1], we now automatically publish builds of Ember Data[2] every time a new commit is pushed that passes our suite of tests.
2. We have begun documenting Ember Data[3] and, while not exhaustive, what we have now is significantly better than just a little while ago. As with what happened with Ember.js, we take documentation very seriously and you should see the Ember Data documentation improve dramatically over time.
3. As we outlined in a recent blog post[4], we are focused on
Read the rest
stabilizing Ember Data and do not have plans for new features at this time. If we made a mistake in the initial API design, it was not providing enough imperative trap doors to use when the declarative APIs were not sufficient. We are working on fixing that.
Thanks to our friends at Addepar, we are able to dedicate several full days per week to Ember Data and you should see the velocity of the project increase significantly. Many observers have noticed the recent flurry of commit activity[5]; this was not an aberration but an indication of what the future holds now that we have daytime hours to dedicate to it.
If you have specific suggestions for how to make Ember Data as approachable as possible, please let me know. Like I said, my focus right now is on eliminating bugs, stabilizing APIs, and making sure new developers don't hit frustrating rough spots.
1: https://github.com/emberjs/data/pull/850
2: https://s3.amazonaws.com/builds.emberjs.com/ember-data-lates...
3: http://emberjs.com/guides/models/
4: http://emberjs.com/blog/2013/03/22/stabilizing-ember-data.ht...
5: https://github.com/emberjs/data/commits/master
I've submitted a PR to em-data which should make the REST support a bit more clear. https://github.com/emberjs/data/pull/834
In Stabilizing Ember DataThanks for the response! Only reason I mentioned it was that I didn't see REST anywhere in the linked article or here: https://github.com/emberjs/data
In Stabilizing Ember DataThanks for the suggestion! In fact, you've just described exactly what we're building. We are big fans of REST, and if you read the documentation, you'll see that the default behavior of Ember Data is to transmit RESTful JSON[1].
In addition, we've been working with a bunch of really smart Rails people like Steve Klabnik and Santiago Pastorino on projects like ActiveModel::Serializers[2] and rails-api[3].
That being said, we know that there are a lot of different ways to serialize and transmit records, so we've designed the architecture of Ember Data such that those decisions are encapsulated in specific objects which we call adapters. You can think of it like the adapters for different databases for ORMs like ActiveRecord.
The default adapter, though, is RESTful JSON, and is what we use in all of our applications. You can see the impleme
Read the rest
That's good to know... though in my hasty research I didn't see anything that said so. That should be a big selling point.
https://github.com/emberjs/data
In Stabilizing Ember Data> It was a mistake to "release" Ember itself as a 1.0 before Ember.Data was ready.
Ember 1.0 was released? Looks like only an rc-1 so far to me.
Also, Ember-data is a distinct project from Ember itself, no? It's in a different repo (https://github.com/emberjs/data) and states "This is definitely alpha-quality. The basics work, but there are for sure edge cases that are not yet handled."
In Why we're moving away from Ember.jsWell it says right on GitHub, "Is It "Production Ready™"?" - "No. The API should not be considered stable until 1.0."
https://github.com/emberjs/data
In Why we're moving away from Ember.jsread-only attributes comes to mind, but that was four months ago and it seems that it's been pretty much worked out here, https://github.com/emberjs/data/pull/303..
Regardless, I still think it's a bit overkill. You'd be surprised to see how much of the basic ember-data functionality you can achieve just by using Ember.A and Ember.Object.
In EmberJS and Confusion, Part 2Yes it does. I have added enough links that touch on that.
https://github.com/emberjs/data
http://emberjs.com/guides/ember-data-lifecycle/
https://speakerdeck.com/tomdale/30 slides for the video below
http://www.youtube.com/watch?v=djhAsWGOImk Tom Dale - Ember-data
https://speakerdeck.com/tchak/ember-data
In Preventing memory leaks in Backbone.jsHave you seen Ember-Data? https://github.com/emberjs/data
In Ember.js 1.0 PrereleaseShowing the 15 most recent of 19 sources. Enable JavaScript to search and browse every indexed mention.