Bilingual software, built and run end to end.
Sunset Atomic is a product studio in Miami. One principal takes a product from the first decision to the servers it runs on — the application, the data model, and the AWS account underneath — for Spanish-speaking businesses and the people who serve them.
Miami, Florida · English and Spanish · Two products running today
Products the studio owns
Two products, built here and operated here.
Not screenshots from someone else's portfolio. Both run on infrastructure this studio maintains, and both state their stage plainly.
Migr8Suite
In production with one firm · Billing not built yet
Case-management software for small US immigration practices. Clients, cases, documents and USCIS status tracking in one place, in English and Spanish. Priced flat per firm rather than per seat, so adding staff does not change the bill.
migr8suite.com
LoroCast
Live with real data · Pre-revenue
A sponsorship brokerage for Spanish-language and bilingual podcasts and creators in South Florida. It also publishes a bilingual public index of podcast promo codes that cites the exact show and episode each code was read on.
lorocast.com
Client work
One engagement, in production since 2025.
A Miami multiservicios business — immigration forms and consular services — hired Sunset Atomic to build its public website. The site runs as static files on AWS S3 behind CloudFront, with automated deploys. Changes have shipped on the firm's instruction continuously since 2025, including one required by Florida law on notaries public.
The same firm is Migr8Suite's live production customer. It moved off a legacy Laravel system.
The client is not named here yet, because it has not agreed to be named.
Read the engagement in full
Under the hood
The infrastructure is part of the deliverable.
These are the practices already running on the studio's own accounts, not a wish list.
-
An AWS organization defined in Terraform
Service control policies, IAM Identity Center permission sets, CloudTrail, budgets and cost-anomaly alerts, and remote state with locking. Plans run on every pull request; applies are gated and authenticate through OIDC, so no long-lived access key exists.
-
Security checks on every pull request
Static analysis, dependency audit and secret scanning. Actions are pinned by commit SHA and given least-privilege permissions.
-
Immutable-artifact deploys
An image is built once and promoted to production by digest. Rolling back is a single configuration change, not a rebuild.
-
Decisions written down
17 architecture decision records and written operational runbooks, so the reasoning survives the person who had it.
-
Bilingual where it counts
The Spanish message catalog is complete on the backend, so validation errors come back in Spanish. That is a different thing from a translated marketing page.
-
A USCIS Case Status API integration
Isolated in its own Lambda so no credential sits in the application or the marketing site. Production access is still an application in progress; production currently points at the USCIS sandbox.
How it works
A short path from first email to running software.
-
Say what you need
One email: what the business does, which language your customers actually use, and what is missing or breaking today.
-
A written scope
What gets built, in what order, and what it runs on. If the work is not a fit, you hear that up front.
-
Build, then run it
The application ships, and the studio keeps operating the AWS account underneath it.
Contact
Write to hello@sunsetatomic.com. It reaches the person who would do the work, not a queue. Say what your business does, which languages your customers and your staff use, and what you want to exist.
Sunset Atomic