Four products, one engine and one led delivery.
Four apps and platforms, an engine that runs every morning at Alistra and a healthcare delivery the founder led. Each example states what the need was, what the solution does and what role Alistra had.
Fyndrutt
A mobile app for finding and planning flea market visits.
Who it is for
People who drive around to flea markets, auctions and yard sales.
The need
The finds are scattered and the opening hours are rarely right. Planning the trip takes as much time as making it.
The most important things it does
- Flea markets and opening hours are fetched automatically from Google Places
- The route is planned along the drive you are making anyway
- Check-in on site is verified against your location
- Points and badges for those who want to collect their trips
Alistra's role
Built by Alistra from the ground up, from data model and routing logic to interface and regulatory compliance.
Status
In development
Technical details about Fyndrutt
Vite, React and Capacitor on Supabase. The points engine runs on the server with duplicate and cheat protection, so a check-in cannot be repeated. Consent, data export and deletion are built in.
Riggd
A platform for gyms, with an app for the members and an admin site for the gym.
Who it is for
CrossFit and Hyrox gyms, and their members.
The need
Booking, memberships, payments and check-in live in different systems. The gym spends time on administration instead of on its members.
The most important things it does
- Class booking with waitlist, punch cards and on-site check-in
- Memberships and payment per gym, with receipts and credit notes
- Programmes and benchmarks, so the coach does not have to rewrite the same workout
- Remote door opening for those with access
Alistra's role
Riggd is being built together with a partner. Alistra is responsible for the build, both the member app and the gym's admin site, and the product is run jointly.
Status
Built with a partner, with a CrossFit gym as its first user.
Technical details about Riggd
React Native and Next.js on Supabase. Each gym is its own tenant and the boundary between them is enforced by the database's access rules, not by the app code. Each gym connects its own payment account.
Recra
A platform that matches people with assignments and jobs.
Who it is for
Job seekers, freelance consultants, consulting firms and those looking for someone.
The need
Applications are judged on how a CV is worded rather than on what the person can do. The person searching has to dig through a pile by hand.
The most important things it does
- Matching that weighs requirements against actual skills, not against keywords in a title
- Skill levels built from a structured interview, not from self-assessment
- Every match saves a readable record of the decision
- Identity is hidden until both parties choose to proceed
Alistra's role
Alistra built the platform from data model and matching engine to payment flows.
Technical details about Recra
Next.js on Supabase, with semantic search in pgvector and language models for the analysis. The decision record is saved because the EU AI Act requires traceability when a system ranks people.
Nexteam
A system for organising tournaments in team sports.
Who it is for
Tournament organisers, team managers and the spectators following the matches.
The need
Registrations, payments and match schedules are often handled in spreadsheets. The schedule is the hard part: pitches, times and rounds have to fit together without clashes.
The most important things it does
- Team managers register teams and pay in the same flow
- A scheduling engine that places groups, rounds and pitches without clashes
- Spectators follow the tournament without logging in
Alistra's role
Nexteam is being built together with a partner. Alistra is responsible for the build, the product is run jointly.
Status
In a test environment
Technical details about Nexteam
Next.js as a Cloudflare Worker on Supabase. The scheduling is our own logic, not an off-the-shelf library.
Every morning, new assignments are sorted.
The engine monitors consulting portals for Alistra. What used to be a daily manual review is today a document to decide on.
- ReadsGoes through the portals every day.
- ExtractsThe mandatory requirements from each assignment.
- SortsAgainst Alistra's own criteria.
- WritesA document. A person decides.
Alistra's role
Built by Alistra for its own use, with the same tools sold to clients: our own code, language models and connections to the sources that need to be read.
The same setup for you
Swap consulting portals for your enquiries, invoices or applications. Each workflow is built against your sources and your criteria.
From undocumented case handling to a solution in production.
Implementation of ServiceNow App Engine for a healthcare administration.
The need and the work
The case handling needed to be documented and turned into a shared set of requirements. Alistra's founder led the mapping and workshops and held the delivery together from needs and requirements to a solution in production.
The founder's role
Project and delivery management with responsibility for delivery, budget and team.
The development
The development team built and configured the solution. Alistra's founder led the work and did not develop it himself.
What do you want to build?
Describe your idea, a workflow or an assignment.