Stalitsa · Capabilities
Capabilities
Languages, edge stack, and tooling Stalitsa uses to deliver real sites and APIs — aligned with what ships in repos and configs (how source is kept private, including for this site, is on About → Source & visibility). Where a brief includes the premises, Stalitsa also scopes on-site IT: small LANs, switches, Wi-Fi placement, and device connectivity for shops and offices.
End-to-end help for public websites, edge-hosted HTTPS APIs, data-backed features and payments when you need them, business email on your own domain, and — where the brief includes the premises — hands-on IT for small shops and offices. Work is scoped in writing, delivered in reviewable steps, and handed over with documentation your team can run without guesswork. Typical engagements span marketing and brochure sites, menus and catalogues with an agreed editing workflow, enquiries and booking-style flows, integrations that stay maintainable, and DNS plus mailbox setup so customers see a professional address. Stalitsa serves retail, hospitality, trades, automotive, professional services, and product-style builds — not a single vertical. Commercial terms and scope are agreed in writing after a short brief — start from Contact.
Languages & full toolset
Programming languages, edge delivery, data, payments, build tooling, and editor-side workflow — grouped so you can scan quickly.
Programming & markup languages
Frameworks, edge & delivery
Data & payments
Build, templates & config
Also: JSON, YAML, TOML in project config, Cloudflare Pages, deployment tooling where projects use it, and related stack-specific files.
Software & day-to-day tooling
Sites & UI
Static delivery, semantics, security headers, and accessible markup.
Static HTML, CSS, and JavaScript on Cloudflare — fast first paint, predictable hosting, and a clear separation between public pages and any admin or tooling you need behind authentication.
Stalitsa builds semantic structure (landmarks, headings, lists, forms) so pages stay understandable in screen readers and search engines; adds sensible ARIA only where it earns its keep; respects focus order and keyboard paths; and ships security headers (for example HSTS and CSP) where the repository defines them. Layouts are responsive across breakpoints, touch targets are considered on small screens, and reduced-motion preferences are not ignored when motion is decorative.
Edge services
HTTPS at the edge — JavaScript or Python on Cloudflare, with FastAPI, Pydantic, and httpx when that split fits; CORS and origin checks for browsers.
HTTPS APIs at the edge on Cloudflare — JavaScript for full request/response handling over TLS, or Python with FastAPI, Pydantic, and httpx when the service layer fits Python and needs to call other HTTPS APIs cleanly.
Routes are designed with validation, structured errors, and logging that helps you diagnose production issues. For browser callers, Stalitsa applies CORS and origin checks deliberately — not “allow everything.” Where APIs accept writes, patterns cover authentication, rate limits, and idempotency for sensitive operations so retries do not double-charge or double-book.
Data & commerce
SQLite-class data on Cloudflare, Web Crypto, HTTPS to payment APIs, rate limits and cache where it stays correct.
SQL-backed tenant data on Cloudflare (SQLite-class stores at the edge), schema and migrations treated as part of the product, and read paths that stay correct under caching.
Payments use Stripe and/or PayPal over HTTPS with hosted checkout flows where that keeps PCI scope small. Stalitsa wires webhooks carefully, handles signatures and replay-aware processing, and applies rate limits plus cache only where responses remain truthful for every client.
Content & delivery
Templates to static HTML, repeatable builds, and CI — plus Lua when a small language fits the job.
Jinja2 templates compiled to static HTML where that pipeline fits; npm scripts and the vendor CLI for environments and deploys; GitHub Actions, Cloudflare Pages, or other hosts so builds and releases stay repeatable rather than one-off rituals.
Branches, review, and secrets outside the repository — CI, hosting dashboards, or vaults — are part of the default bar. Lua appears for small, fast glue (automation, embeddable logic, game-adjacent tooling) when a lightweight language sits better next to heavier stacks than bolting on more complexity.
Business email (Zoho Mail)
Stalitsa helps clients move off generic addresses and run email on their own domain using Zoho Mail — mailboxes, groups or aliases, and the DNS side (MX, SPF, DKIM, DMARC where it makes sense) so messages authenticate cleanly.
DNS is configured so mail sends and lands reliably: MX to the right hosts, SPF to authorise sending sources, DKIM for message signing, and DMARC where it makes sense so spoofing is harder and reporting is honest. Handover includes what to change when you add a new sender or subdomain.
Examples: info@greek-house.uk for a restaurant site like Greek House, bookings@kritamo.co.uk for table enquiries — the kind of addresses customers remember.
On-site IT & small networks
Survey, install, and document small-office or shop networks — with the same handover discipline as the digital side.
For small premises, Stalitsa can survey, design, and install dependable wired and Wi-Fi layouts: cable paths that stay serviceable, switches sized for today with a little headroom, and Wi-Fi placement that respects interference and coverage instead of “one AP in the corner.”
Work often includes a tidy cabinet for router, NAS, or another compact box (shared files, backups, light services), VLAN or guest separation when the brief needs it, and onboarding for staff laptops, phones, printers, POS, guest Wi‑Fi, and tills so everything reaches the internet and each other predictably. You get labelled ports and written notes so staff are not guessing after go-live.
Smart home & protocols
Automation, low-power mesh, and messaging — the stack Stalitsa uses for connected-building work when clients want Home Assistant, Zigbee, and MQTT, together with structured wiring and device commissioning where those are part of the agreed brief.
What Stalitsa focuses on
The delivery bar Stalitsa optimises for — whether the work is in a browser or on a wall in the comms cupboard.
- Edge delivery — Static sites and HTTPS APIs on Cloudflare, CI so deploys stay repeatable.
- HTTPS & trust — Security headers, CSP where defined, careful CORS, solid auth patterns when APIs need them.
- Product plumbing — Data on Cloudflare, Stripe/PayPal over HTTPS, caching only where it stays correct.
- Business email — Zoho Mail on client domains (e.g. info@greek-house.uk, bookings@kritamo.co.uk): setup guidance and DNS so mail sends and lands reliably.
- On-site IT — Switches, LAN and Wi-Fi for small shops or offices, compact cabinet installs (router, NAS, light on-prem roles), and onboarding phones, laptops, printers, and POS onto the network.
- The web surface — Responsive, structured markup; accessibility as a default bar.
Exact stack for a project depends on requirements — Stalitsa recommends the smallest approach that stays maintainable.