ENPT

Tech Byte Frontier — independent software house, Brazil

Software that survives contact with reality.

We design and ship production systems — Rust engines, real-time platforms and AI-assisted products — for people who need software that works on Monday, not in the demo.

> START A PROJECT> VIEW THE WORK

Problems we were handed. Systems we handed back.

Rental operations dashboard with revenue charts, property summaries and a booking calendar.

Hospitality · Brazil · Under NDA

Short-Term Rental Operations Platform

Before
An operator running multiple Airbnb properties was losing hours every week to manual revenue tracking, expense spreadsheets, and paper receipts.
After
Weekly ops time back. Bookings and expenses land in the books without re-keying.

A web app operators log into every day: capture documents, review what the system extracted, and keep books current. Unclear documents can still be checked by a human before they post.

Timeline
From discovery to a usable beta in under a quarter, then quality improved after the first live week.
Stack
  • React
  • Hono
  • Supabase
  • Anthropic
  • Fly.io
Read the case

What operators say after ship.

“We stopped drowning in booking PDFs. The books just update, and I got my Sunday back.”
Ops lead, Hospitality ops · BR
“Not a black box. Every rebalance is auditable, and the backtest harness paid for itself before we touched live capital.”
CTO, Digital assets
“Local-first was non-negotiable. Custom classifiers on our machine, charts that keep up, no cloud tax.”
Quantitative researcher, Capital markets

Full-stack in the literal sense.

Full capabilities

Our own products, not just client work.

JevGate is public: read the source, install it and judge the engineering before you ever talk to us.

Public on crates.io

JevGate

A code-review gate. It parses your repository locally into small units of evidence, asks TypeSafe Jev short typed questions about each, and lets code — not a chat model — combine the answers into findings with a location, a probability and a next step.

Written in
Rust
License
MIT / Apache-2.0
GitHub crates.io 
$ cargo install jevgate --locked$ jevgate check --base origin/main JevGate: consider · gate passed · 42 files · 118 API requests Consider (2):  src/billing/invoices.ts:88 [maintainability/shared-logic] `createInvoice` and `createReceipt`    perform the same steps for the same purpose (0.93). Differences: `invoices`→`receipts`.    → Move the shared steps into one implementation  src/api/search.py:41 [security/injection] `search_orders` places its parameters into a    database query without binding, escaping or checking them; a caller passing outside    input would make it exploitable (0.88).    → Pass the values as bound query parameters
Example run, from the JevGate README.

Browser MMO · In development

Nodehaven Online

A persistent medieval world designed around player-run towns and a player-driven economy — 3 regions, 90 districts, 4,500 world nodes. Authoritative state in SpacetimeDB; JevGate review is a required check on its pull requests.

Get playtest updates

Who you are wiring money to.

Tech Byte Frontier is an independent software house based in Brazil, working remote-first. We lead with engineering (systems, products, and applied AI) and we stay small on purpose so accountability never gets diluted.

  • Proof over atmosphere

    Working software, auditable decisions, and outcomes you can point at. Not theater.

  • Constraints first

    NDA, local-first, latency, budget: we name the hard edges before we estimate.

  • Ship and stay reachable

    Deployed, documented, handed over. We do not vanish the week after launch.

No black box. No surprises.

Read the handbook

  1. Discover

    A conversation, not a questionnaire. We map the problem, the constraints, and what done means together.

    You get: a shared definition of done

  2. Propose

    You get scope, timeline, and price in writing before anything starts. No open-ended meter running.

    You get: written scope, timeline and price

  3. Build

    Short cycles with working software from week one. You review progress as it happens, not at the end.

    You get: working software each cycle

  4. Ship

    Deployed, documented, handed over. And we stay reachable after launch.

    You get: a deployed, documented system

Engagement models

We do not publish fake price tables. A real quote follows a real conversation about constraints.

  • Fixed scope

    Clear problem boundary, written deliverables, fixed price. Best when the edges are known enough to estimate honestly.

  • Time & materials

    Weekly or bi-weekly cycles with a shared backlog. Best when discovery is still moving or priorities will shift.

  • Retainer

    Reserved capacity for ongoing product work, rescue, or platform ownership. Cadence and response expectations written up front.

Straight answers before the call.

How do engagements work?

Discover → Propose → Build → Ship. You get written scope, timeline, and price before build starts. Fixed scope, time & materials, or retainer: matched to the problem, not a one-size product SKU.

Do you sign NDAs?

Yes. Client work on this site is anonymized by default. We treat code, data, and business context as confidential.

How long until something real ships?

Working software from early cycles. Not a three-month dark period. Exact timelines depend on scope; we put dates in the proposal.

Are you remote?

Based in Brazil, remote-first. We collaborate async with clear written artifacts and scheduled syncs when they earn their place.

What stacks do you prefer?

Rust where systems demand it; TypeScript/React for products; Python for ML harnesses and data work; Postgres and SQLite as default data stores. We pick for the constraint, not for a resume.

What do you not do?

We are not a staffing body shop, a pure design agency, or a slide-deck consultancy. If the engagement is mostly meetings with no path to production software, we will say so.

Open a channel.

A system that needs building, or one that needs rescuing. Send the brief — we respond within 24 hours.

Email
contact@techbytefrontier.com
GitHub
Tech-Byte-Frontier
LinkedIn
Tauan Binato

2–3 sentences: the problem, the constraint that matters most, and a date if there is one.

Your data is private and safe. Need an NDA first? We sign them.

CONTACTLIVE

SIGNAL RECEIVED

CHANNEL OPEN

Your brief is on the wire. We respond in under 24 hours, usually sooner.

No ticket black hole. A human on the critical path will write back.

> handshake ........ OK

> brief stored ...... OK

> response SLA ...... < 24H