Skip to content

YAPI S.A.S. · Atuntaqui, Ecuador

Vertical software for SMBs, on one shared platform.

We build SaaS products for small and mid-sized businesses in Ecuador and Latin America. They all share the same foundation — identity, per-customer data isolation, SRI e-invoicing — so every new product starts with the hard parts solved and per-customer costs stay low.

Our goal: production-grade AI for businesses that rarely have access to it.

  • YAPI Loyalty Customer loyalty
  • YAPI Fleet IT asset audits
  • YAPI Next vertical

YAPI Platform

  1. Per-customer data isolation
  2. Identity and access
  3. SRI e-invoicing
  4. Subscriptions and credits

PostgreSQL · row-level policies

YAPI S.A.S. Sheet 00 Platform cross-section Rev. 2026·10

01 Platform

Solve the hard parts once.

A small business needs what a large company needs — security, invoices the tax authority accepts, protected data — without paying what it costs to build. So every YAPI product stands on the same platform instead of reinventing it.

Our stack: Laravel, Filament, PostgreSQL, Go and Rust, with interfaces in Astro, Next.js and Expo.

  1. Per-customer data isolation

    Each business sees only its own data. In the core platform and in YAPI Loyalty that does not rest on application code alone: the database itself enforces it with row-level security policies.

    PostgreSQL · forced Row-Level Security

  2. Identity and access

    One registry of users, organizations and roles for every product, with an admin panel for each customer.

    Laravel 12 · Filament v5

  3. SRI e-invoicing

    A dedicated service signs invoices, submits them to Ecuador's tax authority (SRI) and tracks their authorization. A transactional queue keeps any invoice from getting stuck halfway.

    Go · XAdES-BES · transactional outbox

  4. Subscriptions and credits

    Plans, payments and usage credits — WhatsApp messages, for example — shared by every product instead of rebuilt for each one.

    Shared billing schema

02 Products

Two products, one foundation.

Each product solves one concrete problem for one kind of business, and inherits security, invoicing and data isolation from the platform.

YAPI Loyalty

Deployed · pre-launch

Digital stamp-card loyalty

The paper stamp card, now on the customer's phone. The cashier records each purchase with a QR code; customers collect stamps, keep them in Google Wallet and get reminders on WhatsApp.

Customer
Card in Google Wallet and on the web, nothing to install
Counter
Yapi Caja app to record stamps and redemptions
Messaging
WhatsApp reminders and web notifications
Control
Anti-fraud rules and multiple branches per business

YAPI Fleet

In pilot

Technical audits of IT equipment

Measures every Windows computer in an organization and issues a Technical Needs Report: which machines are worth upgrading, which should be replaced, and why — with every criterion cited.

Measurement
~1 MB collector; works offline, from a USB drive
Integrity
Every measurement is signed (Ed25519), and the report states whether it was verified
Criteria
OS support, Windows 11 eligibility, memory, disk health, service life and processor
Privacy
Nothing about users: no accounts, sessions or files; the report never names brands

The platform is designed to take on more verticals. We will announce them when they exist, not before.

03 How we use Claude

Claude in engineering today; in the product, step by step.

We are a deliberately small team: development is led by a technical founder working with Anthropic's Claude. We use it where it already delivers, and we say plainly what is still being built.

In use

Software development and code review

Claude Code writes and reviews the code in all of our repositories. To do that with discipline we built our own governance layer: per-stack rules, agents that review every change — code, security and decisions — and automated checks on every commit.

  • Company rules (per-customer isolation, data protection, SRI) loaded into every session
  • Isolated reviewers; a merge carrying unreviewed decisions is blocked
  • Checks that block, before the commit, code that could cross data between customers
  • In development

    In-product analytics

    Plain-language questions about the business's own data, without leaving per-customer isolation.

  • In development

    Operational document summaries

    Reading and summarizing invoices, technical reports and other documents that are reviewed by hand today.

  • In development

    AI-assisted automation

    Repetitive tasks for client businesses handled with AI assistance, always with a person who approves.

The goal stays the same: production-grade AI at a per-customer cost a small business can afford.

04 Trust and compliance

Built for Ecuador's law from the start.

Trust is not added at the end. These safeguards live in the platform, so every product has them from day one.

  • LOPDP

    We handle personal data under Ecuador's Personal Data Protection Law (LOPDP): sensitive data encrypted in the database and a direct channel to exercise your rights.

    dpo@yapi.ec

  • Per-customer isolation

    In the core platform and in YAPI Loyalty, the database prevents one customer from reading another's data. On top of that, automated checks on every commit look for code that could bypass that isolation.

    Row-level policies · checked on every commit

  • SRI

    XAdES-BES electronic signatures, with each issuer's certificate stored encrypted under its own key, and every exchange with the SRI logged for audit.

    AES-256-GCM · submission log

  • Operations

    Every change passes automated checks before it reaches production. Backups are kept off the server, and restores are rehearsed and timed.

    Off-site backups · restore drills

05 Contact

Let's talk about your business.

If you run a small business, are considering a pilot, or invest in software for Latin America, write to us. We will reply by email.

Atuntaqui, Imbabura, Ecuador