Skip to main content
繁中EN日本語

We turn recurring operationsinto durable products

openinfo is not a one-off website shop. We operate our own SaaS products and data platforms, turning content publishing, data collection, access control, scheduled jobs, API integrations, and monitoring into systems that keep running.

View owned productsTalk to us
Openinfoteam

A product operating team that proves engineering capability in production.

Our core team has long worked across enterprise information systems, mobile applications, platform services, and public-sector or large-enterprise collaboration. What we bring is not only frontend and backend delivery, but the full chain of analysis, architecture, data governance, workflow digitization, admin tooling, security controls, acceptance testing, and operational handoff.

Requirements and system architecture
Frontend/backend integration and admin tooling
Multi-source data governance
Workflow digitization and operating documents
Security controls and access design
Acceptance testing and operational handoff

Owned products. Transferable capability.

fb-commander and house-miner are where openinfo has hardened the backend, data, access-control, scheduling, and operations work that future projects can reuse.

fb-commander

Real estate social operations automation

A platform for real estate operators to manage multiple Facebook accounts, configure recurring or randomized publishing strategies, and automatically distribute listings, images, and videos to selected groups and social channels.

  • Multi-account and channel management
  • Recurring and randomized publishing
  • Social post and media intelligence
  • RBAC permissions and API integration
Publishing operationsfb-commander
  1. 01 InputGoogle Cloud service: Cloud Storage

    Accounts and media

    Facebook accounts, listings, images, and videos are organized as publishing material that can map to Cloud Storage-style retention and delivery.

    • Accounts
    • Listings
    • Media
  2. 02 PlanGoogle Cloud service: Cloud Scheduler

    Publishing strategy

    Recurring and randomized rules set the publishing rhythm, and can map to Cloud Scheduler-style cloud triggers.

    • cron
    • randomize
    • manual run
  3. 03 RunGoogle Cloud service: Pub/Sub

    Worker publishing

    Jobs can be decoupled through Pub/Sub, executed by Cloud Run / workers, and reported back with target-level publishing status.

    • queue
    • publisher
    • SSE
  4. 04 OutputGoogle Cloud service: Cloud Run

    Social channels

    Posts and media go to selected groups and channels, while execution results remain visible to the team.

    • Groups
    • Channels
    • Logs
FB Commander post management workspace screenshot

house-miner

Real estate data infrastructure

A data infrastructure platform that extends fb-commander's collection capability, continuously integrating listings from 591, Facebook groups, LINE groups, agency websites, and other public sources into a searchable historical data warehouse.

  • 591 / social / website source integration
  • Historical warehouse and search
  • Data-First preservation
  • Standardized API for enterprise systems
Rental intelligencehouse-miner
  1. 01 SourceGoogle Cloud service: Cloud Functions

    Multi-source input

    Listings are collected continuously from 591, Facebook groups, LINE groups, agency sites, and public sources.

    • 591
    • FB / LINE
    • Websites
  2. 02 CollectGoogle Cloud service: Dataflow

    Collection jobs

    Crawling and processing run as observable background jobs that can map to Pub/Sub / Dataflow-style cloud data pipelines.

    • crawler
    • queue
    • worker
  3. 03 StoreGoogle Cloud service: BigQuery

    Historical data plane

    Normalization, deduplication, and file retention can connect PostgreSQL, Redis, and MinIO while extending toward BigQuery / Cloud Storage-style warehouses.

    • PostgreSQL
    • Redis
    • MinIO
  4. 04 ActivateGoogle Cloud service: Cloud Monitoring

    Search and alerts

    Rental clusters become searchable and trackable, with alerts sent to Telegram, Discord, or APIs.

    • cluster
    • alerts
    • API
House Miner 591 rental history lookup screenshot

From source configuration to visible operational result.

Workflow

  1. Source contract

    Define the source

    Select social channels, 591, LINE, websites, or existing system entry points and turn them into repeatable source contracts.

  2. Queued job

    Queue the work

    Scheduled or manual jobs enter the queue with parameters, timing, and actor context instead of living only in the interface.

  3. Observable run

    Execute with workers

    Background workers publish, crawl, normalize, or integrate while the interface stays focused on operation and review.

  4. Evidence

    Review the result

    Screens, notifications, and logs report success, failure context, and next actions so operations stay traceable.

Shared product capabilities

The same engineering base powers both products.

  1. 01
    Operate

    Operational admin and access control

    Products need accounts, roles, feature permissions, and audit trails that support team operations instead of single-user screens.

    • Roles
    • Audit trail
    • Team operation
  2. 02
    Execute

    Scheduled jobs and worker boundaries

    Publishing, crawling, and processing move into observable background jobs: the interface drives work, while workers execute it reliably.

    • Schedules
    • Queues
    • Worker boundary
  3. 03
    Preserve

    Data cleanup and historical retention

    Multi-source inputs are normalized, deduplicated, retained, and indexed so data becomes an operating asset rather than a snapshot.

    • Normalize
    • Deduplicate
    • Historical search
  4. 04
    Handoff

    APIs, monitoring, and handoff evidence

    Systems must connect to existing workflows while keeping execution records, error context, health signals, and maintainable delivery evidence.

    • APIs
    • Health signals
    • Delivery evidence
Transferableengineering

We turn prior system work into engineering methods the next project can use.

Our project experience spans AI video data flows, media asset management, international order systems, mobile applications, and airport workflow digitization. These projects inform how openinfo handles data governance, workflow redesign, system integration, admin tooling, APIs, acceptance testing, and operations handoff.

01
Data stream

Realtime data and event retention

AI snapshots, alert images, video clips, and device status were structured into searchable, replayable operating data.

  • snapshots
  • alert images
  • event replay
02
Data model

Data model and quality constraints

Inconsistent naming, duplicates, and logical conflicts were redesigned into maintainable structures for search and reporting.

  • field rules
  • dedupe checks
  • search model
03
Integration

Cross-system workflow integration

Orders, mobile devices, permit reviews, and legacy integrations were handled through clear data models, APIs, and acceptance rules.

  • APIs
  • review flow
  • acceptance
04
Handoff

Operations-aware delivery

Testing, automation, security controls, operating guides, and maintenance records are treated as part of the delivery surface.

  • testing
  • runbooks
  • ops records
Does your workflow repeat every day?

If sources are scattered, manual work is piling up, and ad hoc maintenance is not enough, we can help shape it into a product.

Back to top

透明資訊有限公司

OPENINFO LTD.
Contact
張震龍
Company address
13F, No. 8, Sec. 1, Keelung Rd., Songshan Dist., Taipei City
Phone
0908350210
Email
twkevinzhang@gmail.com

OPENINFO.TW© 2026 OPENINFO LTD. All rights reserved.