NocoDB: Turn PostgreSQL into Airtable in 1 Day

NocoDB: Turn PostgreSQL into Airtable in 1 Day

We integrate NocoDB with your relational database — PostgreSQL, MySQL, or SQLite. It’s an open-source platform that provides an Airtable-like interface without writing a single line of code. The key difference from Baserow or SeaTable: NocoDB connects to your existing database and displays real tables, not creating separate storage. Your production data stays put, and non-technical employees get a convenient spreadsheet to work with.

Over the years, we've set up NocoDB for dozens of projects: from a CRM for a sales department to a logistics monitoring dashboard. Our experience shows that 80% of internal tasks can be covered without writing code — just configure permissions correctly, create forms, and connect webhook notifications.

How NocoDB Solves the Problem of Custom Admin Panels

Custom panels built on Laravel or Django require months of development and constant maintenance. NocoDB provides a ready interface in one day, and through REST/GraphQL API you can extend functionality when truly needed. Compare: the average cost of a custom admin panel starts from $4,000 and takes 2 months. NocoDB costs a fraction — you pay only for setup and integration. Below is a comparison:

Why Choose NocoDB for Internal Tools?

The main reason is speed and security. You don’t write code but control data. NocoDB allows rapid prototyping of interfaces, then expansion via API. For example, one logistics client replaced three Excel sheets with a single dashboard in 2 days — saving 15 hours per week.

Setting up Access Permissions: Detailed Breakdown

After connecting to the DB, configuring permissions is critical. We use two levels: at the NocoDB level (table roles) and at the DBMS level (database users). For most tables, we create a separate read-only user:

-- Read-only for most tables
GRANT SELECT ON ALL TABLES IN SCHEMA public TO nocodb_readonly;

-- Allow editing only for specific tables
GRANT SELECT, INSERT, UPDATE ON customer_notes TO nocodb_rw;
GRANT SELECT, UPDATE ON users TO nocodb_rw;

REST API: Auto-Generated Endpoints

After connecting, each table gets its own API. Swagger documentation is available. Example requests:

# List records with filter
GET /api/v1/db/data/noco/{PROJECT_ID}/{TABLE_ID}?where=(status,eq,active)&limit=25&offset=0

# Create record
POST /api/v1/db/data/noco/{PROJECT_ID}/{TABLE_ID}
{"name": "John", "email": "[email protected]", "status": "new"}

# Bulk update
PATCH /api/v1/db/data/bulk/noco/{PROJECT_ID}/{TABLE_ID}
[{"id": 1, "status": "processed"}, {"id": 2, "status": "processed"}]

The API supports all CRUD operations, filtering, sorting, and pagination. This allows integrating NocoDB with any external service or creating custom React/Vue interfaces.

No-Code Data Collection Forms

A public form from any table is a killer feature. An employee sends a link to clients, data goes directly into the DB. Use cases:

• Client requests → leads table
• Employee reports → daily logs
• Feedback collection → feedback table

Forms are configured in a few clicks: select fields, mark required, customize design. No code needed.

What Are Webhooks and How to Set Them Up?

A webhook automatically notifies an external service when data changes. In NocoDB, this takes 5 steps:

1. Go to table settings → Webhooks → Add New.
2. Choose event (after insert / after update / after delete).
3. Enter the URL of your server.
4. Configure headers (e.g., secret token for verification).
5. Save. Now each change triggers a POST request with data.

Example handler in Node.js:

app.post('/hooks/nocodb/leads', async (req, res) => {
  const { type, data } = req.body;

  if (type === 'records.after.insert') {
    const lead = data.insertedRows[0];
    // Create contact in CRM
    await crmApi.createContact({
      email: lead.Email,
      name: lead.Name,
      phone: lead.Phone
    });
    // Notify manager in Telegram
    await telegramBot.sendMessage(MANAGER_CHAT_ID,
      `New lead from ${lead.Name} (${lead.Email})`
    );
  }
  res.sendStatus(200);
});

Webhook triggers on insert, update, or delete. We've set up chains: new lead → contact in CRM + manager notification + task in Trello. All works without human intervention.

What's Included in the Work

• Connecting NocoDB to your existing database (PostgreSQL/MySQL)
• Configuring access permissions: read-only for tables, editing for selected ones
• Developing data collection forms
• Creating REST/GraphQL API and webhook integrations
• Operational documentation and employee training
• Guarantee of correct operation for 30 days after handover

Our team has years of experience in business automation (over 50 projects). Engineers are certified in AWS and PostgreSQL.

Timeline and How to Start

Connecting to an existing database + permissions + first interfaces — 1-2 days. If integration with CRM, Telegram, or other services is needed — up to a week. Exact timelines are calculated after analyzing your DB and interviewing the team.

Want a consultation? Contact us — we'll evaluate the project for free and offer an optimal solution. Order NocoDB setup today and get a ready internal tool without extra costs.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.