Skip to content
FENIX
Start a project

Jakarta, Indonesia · hello@fenixtechnology.id

Two engagement slots open

Web, systems and mobile engineered to outlive the launch.

CV Fenix Technology is a senior engineering studio led by Cong Fandi. We have shipped 110+ products across four continents — for Indonesia’s new capital authority and national grid, and for product teams in Sweden, the Nordics and the United States.

Founded
2019
Jakarta, Indonesia
Reach
4
continents served
Clients
110+
national & international
In-house
3
live products

GMT+7 — overlapping EU mornings & US evenings

Trusted by

IKN.GO.ID PLN HARPA FIKA CONNECTS NOVA CIRCLE ABERSOFT VEILKEY KICKVOTE AI BODY BUILDER

110 +

Products shipped

web, systems & mobile

10 +

International clients

EU · Nordics · US · APAC

100 +

National clients

government & enterprise

7 yrs

In production

since 2019

Capabilities

One team for the whole stack.

Most clients arrive with a single problem and stay for the rest. Design, engineering, infrastructure and the operations after launch sit under one roof — and one accountable partner.

Web Platforms

01

Marketing sites, portals and SaaS front-ends built for speed and search. Astro, Next.js, Nuxt and Laravel — measured against Core Web Vitals, not opinions.

  • Astro
  • Next.js
  • Laravel
  • Tailwind

Enterprise Systems

02

ERP, billing, asset and dashboard systems that carry regulated workloads. Role-based access, audit trails, integration with the legacy estate you cannot switch off.

  • PostgreSQL
  • Node
  • Go
  • REST & GraphQL

Mobile Applications

03

Cross-platform apps from first commit to store release — Flutter and React Native, with the release engineering and store pipelines that keep shipping weekly.

  • Flutter
  • React Native
  • iOS
  • Android

AI & Automation

04

Practical machine intelligence: computer-vision features, LLM assistants and retrieval pipelines wired into products people already use.

  • Vision
  • LLM
  • RAG
  • Pipelines

Cloud & Reliability

05

Infrastructure as code, CI/CD, observability and on-call runbooks. Deployments that are boring on purpose.

  • AWS
  • GCP
  • Cloudflare
  • Docker
Selected clients

From a national grid to a Swedish software house.

Public infrastructure and private product teams hold us to the same bar: ship it, document it, keep it running. A selection of the work we can name.

Further references — including work under NDA — available on request.

How we work

Four phases. No theatre.

The same sequence for a national utility and a seed-stage product. It is unglamorous, and it is why estimates hold.

  1. I

    Discover

    One week, senior only. We map the domain, the constraints and the integrations, and write down what success measures look like before anyone opens an editor.

    Scope, risks, fixed estimate

  2. II

    Architect

    Data model, service boundaries, auth, environments and the release path. Decisions are documented so the third engineer to join reads the same story as the first.

    Architecture & delivery plan

  3. III

    Build

    Two-week increments against a staging URL you can open any day. Code review on every change, tests where they earn their keep, no surprise at the demo.

    Shippable increments

  4. IV

    Operate

    Monitoring, alerting, runbooks and a named engineer who answers. We stay after launch, because launch is when the interesting failures arrive.

    SLA, observability, on-call

Four promises we
put in writing.

Senior hands only
The engineer in the kick-off is the engineer writing the code. No hand-off to a junior bench.
You own everything
Source, infrastructure, credentials and documentation are yours from day one. No lock-in, ever.
One accountable partner
A single point of ownership across design, engineering and operations — one throat to choke.
Written down
Architecture decisions, runbooks and handovers in writing. Institutional memory outlives contracts.
CF FENIX · Founder
Cong Fandi Founder & Principal Engineer
From the founder

“We do not sell hours. We take responsibility for the outcome — the architecture, the release, the uptime at 3 a.m. That is the only reason a national utility or a Swedish software house keeps a partner ten thousand kilometres away.”

Cong Fandi has led web, enterprise-system and mobile engineering for clients on four continents — from Indonesia’s new capital authority and the national electricity utility to product teams in Sweden, the Nordics and the United States.

  • Led delivery for Indonesia’s new capital authority (IKN) and PLN’s HARPA platform
  • Long-running engineering partner to Abersoft (Sweden), Fika Connects and Nova Circle
  • Founder of VeilKey, KickVote and AI Body Builder
  • Hands-on across web, enterprise systems, mobile and cloud infrastructure

Cong Fandi

Founder & Principal Engineer
CV Fenix Technology

Engagement models

Three ways to work with us.

Every engagement starts with a conversation and a written scope. No retainer traps, no minimum term beyond the work agreed.

Product Build

Fixed scope

A defined platform, system or app taken from discovery to production release.

  • Discovery & architecture
  • Design + engineering
  • Launch & handover
  • 90-day warranty
Enquire
Most chosen

Embedded Team

Monthly retainer

A senior squad inside your workflow — your board, your standups, our delivery discipline.

  • 2–6 senior engineers
  • Your tooling & rituals
  • Fortnightly increments
  • Named tech lead
Enquire

Rescue & Scale

Assessment first

For a build that stalled or a system straining under load. Audit, stabilise, then accelerate.

  • Codebase & infra audit
  • Stabilisation sprint
  • Performance & cost work
  • Roadmap to hand back
Enquire
Questions

Answered plainly.

The things prospective clients ask before the first call.

How do you work with clients in Europe and the US?

We run on GMT+7, which overlaps European mornings and US evenings. Every engagement has a written communication contract: async by default in your own tooling, a fixed weekly call, and a named engineer who answers within one business day. Ten-plus international clients have run this way for years.

Who actually writes the code?

Senior engineers, led by the founder. The person who scopes your project stays on it. We do not staff a project with juniors after the sales call.

What happens to the code and infrastructure?

It is yours from the first commit. Repositories live in your organisation, cloud accounts are in your name, and handover includes architecture notes and runbooks. Leaving us should cost you nothing but the goodbye.

Can you take over a project someone else started?

Yes — that is our Rescue & Scale engagement. We begin with a paid audit of the codebase, infrastructure and delivery process, then give you an honest assessment: stabilise, refactor, or rebuild. Sometimes the honest answer is that you do not need us.

How quickly can you start?

Discovery usually starts within two weeks. Full squads need three to four weeks of notice. Urgent production incidents on existing systems are handled immediately.

Start here

Tell us what you
need built.

You will hear back from a senior engineer — not a sales desk — within one business day, with an honest read on scope, timeline and whether we are the right partner at all.

Studio
Jakarta, Indonesia
GMT+7 — overlapping EU mornings & US evenings
Response time
Within one business day
What do you need?
Indicative budget

Your details stay with us. We never share or sell enquiry data.