Tuqo + Appwrite
Appwrite is an open-source backend (database, auth, files, functions), self-hosted or in the cloud. The front end connects with the browser SDK using the public endpoint and project ID; permissions control access to the data. Tuqo serves the static front end.
What Tuqo + Appwrite gives you
- A document database, auth and file storage
- A browser SDK that works from a static site
- Open source: self-host it or use Appwrite Cloud
- Flexible permissions on collections and documents
Set up Appwrite
Appwrite Cloud or self-hosted: create a project and copy the endpoint and project ID.
Configure permissions
Set access rights (roles or users) on your collections. That is what protects the data.
Add the Web SDK
appwrite (npm or CDN), then Client().setEndpoint().setProject().
Deploy to Tuqo
The site on name.tuqo.ru works with Appwrite directly.
import { Client, Databases } from 'appwrite'
const client = new Client()
.setEndpoint('https://cloud.appwrite.io/v1')
.setProject('PROJECT_ID')
const db = new Databases(client)
const res = await db.listDocuments('DB_ID', 'COLLECTION_ID')Security
The endpoint and project ID are public. Access to the data is controlled by Appwrite permissions (roles on collections and documents); also add your site's domain to the project's allowed platforms. Setting up permissions is your part.
Tuqo serves the front end over HTTPS and never touches your data or the service's secrets.
Tuqo + Appwrite — frequently asked questions
Is there anything to hide? +
The endpoint and project ID are public. Security comes from Appwrite permissions and the list of allowed platforms (domains).
Self-hosted or cloud? +
Either: Appwrite Cloud or your own server. In both cases Tuqo hosts only the front end.
Does auth work from the browser? +
Yes, the Appwrite Account API is designed for client-side auth.