# Not built in

Some features other frameworks offer aren't part of Jadpo, because the
compiler gains little by knowing about them. You build them from your
app's own data and packages, or they come later:

| Feature | Why not, or not yet |
|---|---|
| Realtime subscriptions | Policy on a live stream of changes is a large design, so it comes later. Until then, clients poll with the revision header ([Write revisions](write-revisions.md)) |
| Generated admin screens | Jadpo makes backends, not interfaces. Operators use `jadpo` commands ([The `jadpo` command](the-jadpo-command.md)); a screen can come later on the same operations |
| Payments | Money moves at the provider, so an integration plus [webhooks](webhooks.md) ([Integrations](external-services.md)) is the right shape, and the compiler gains nothing more |
| Content management | Content is application data |
| Product analytics | Events and metrics above feed whichever tool a team uses |
| Quotas and plan limits | A plan's limits are application data, checked by an action; counting uses [counters](counters-and-other-one-step-updates.md) |
| Background job dashboards | Already the operator commands ([Commands for background work](commands-for-background-work.md)) |