Frequently Asked Questions

General

What is Airsequel?

Airsequel automatically generates a complete GraphQL API and provides a spreadsheet UI, a SQL workbench, cloud functions, and a dashboard builder for your SQLite databases and CSV files. You upload or create a database, and Airsequel gives you a backend plus a UI to work with it — without writing any boilerplate.

Do I need an account to try it?

No. You can create a database and start using Airsequel without signing up. Anonymously created databases are public and expire after 10 days. To keep a database permanently and make it private, assign it to a team — which does require an account.

Why is Airsequel built on SQLite?

SQLite is the most widely deployed database in the world. It's fast, extremely well tested, fully featured, public domain, and supported until at least 2050. Because each Airsequel database is a single, standard SQLite file, you're never locked in: you can export it at any time, work on it with your own local tools, and upload it again later. See Databases for the full reasoning.

Who makes Airsequel?

Airsequel is developed by Feram.

Editions & Pricing

Which editions are available?

See the pricing page for the full feature-by-feature comparison and current limits.

Is there a free plan?

Yes. The Free edition includes the GraphQL API, the SQL workbench, CSV uploads, SQLite views, and daily backups, with limits such as 10 tables per database, 2000 rows per table, and a 10 s SQL timeout. Cloud functions and SQLite-file uploads require Pro or higher.

How much does Pro cost?

Pro is $4.10 / month / team when paid annually ($4.50 / month / team when paid monthly). It raises the limits (e.g. up to 100 tables and 1 000 000 rows per table) and unlocks cloud functions and SQLite uploads.

Can I run Airsequel on my own infrastructure?

Yes — that's the Enterprise Server edition. It is self-hosted on your own infrastructure under your own domain, with configurable limits and no dependency on the shared cloud. Contact sales@feram.io for an offer or to request a trial instance.

Is Airsequel open source?

The core engine, AirGQL — the library that generates a GraphQL API from any SQLite database — is developed in the open at github.com/Airsequel/AirGQL. It can be used as a Haskell library or as a standalone CLI server.

Databases & Data

Where is my data stored?

For the shared Free and Pro editions, data is hosted in Germany (Nuremberg). Enterprise Cloud can be deployed to any fly.io region, and Enterprise Server runs wherever you choose to host it.

Can I get my data out?

Always. An Airsequel database is a regular SQLite file that you can export at any moment. We keep your file intact and modify it in the most straightforward way possible, so there is no proprietary format and no lock-in.

What is the metadata.sqlite file?

Some features Airsequel needs aren't part of SQLite itself — table/column ordering, descriptions, and data for charts, dashboards, and cloud functions. We store these in a separate metadata.sqlite file per database so that your actual data file stays clean and portable.

How do I upload data?

Through the web UI, or with the Airput CLI tool for uploading data and files from the command line. The Free edition accepts CSV uploads; SQLite-file uploads require Pro or higher.

Does Airsequel support more than SQLite's basic types?

Yes, via a backwards-compatible convention: column-type suffixes such as TEXT_EMAIL or TEXT_COLOR refine the type while still using standard SQLite type affinity. The UI then shows specialized inputs (e.g. a color picker). See the SQLite-Extra-Types specification.

API & Functions

How is the GraphQL API generated?

Airsequel analyses your database schema and automatically builds the matching GraphQL schema and resolvers, supporting CRUD operations as well as filtering and pagination. A GraphiQL playground is included for every database. See GraphQL API.

How does it compare to Hasura?

The query/mutation shapes are similar, with some intentional differences (e.g. how primary-key updates and naming conflicts are handled). See the comparison with Hasura.

What languages can cloud functions be written in?

TypeScript (executed with Deno) or Python 3.10. Each function gets a JSON request and returns a JSON response, so you don't have to implement an HTTP server. Limits are 256 MB RAM and a 10 s execution time per call, with the last 500 invocations retained for logs. See Functions.

Support & Privacy

How do I get help?

Free-edition users have the self-serve documentation. Pro includes email support, and the Enterprise editions add phone and on-site options. You can always reach us at support@feram.io.

A cloud function can't reach an external URL — what do I do?

Outbound network access from functions is allowlisted. If you hit a PermissionDenied / Requires net access error, email support@feram.io with the URL and we'll review and allowlist it if it's safe.